Safety Incidents OSHA Severe Injury Reports · 2015–2025
2,098,129Injury reports 132,232Establishments Most recent incident 2025-12-31

Berkeley, CA —

OSHA Injury Report: Berkeley Bowl Main

Injury · Job transfer or restriction

At a glance

On , an injury at Berkeley Bowl Main in 2020 Oregon Street, Berkeley, CA 94703 resulted in job transfer or restriction. Employee was cook in supermarkets.

Watch Berkeley Bowl Main — free Get an email when a new federal OSHA severe-injury report for Berkeley Bowl Main is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
Berkeley Bowl Main
Parent company
Berkeley Bowl Produce, Inc.
Street
2020 Oregon Street
City
Berkeley
State
CA
ZIP
94703
On-site location
At the prep table by the dishwasher area in the kitchen.

What was the outcome?

Outcome
Job transfer or restriction (code 3)
Type
Injury (code 1)
Days restricted or transferred
3

Before the incident

Putting trays of ribs and chicken into the oven

What happened

While lifting trays of meat to cook in the oven he had muscle spasms in the neck and shoulder on the right side.

Injury or illness

Sprain of right shoulder

Object or substance involved

Lifting trays of meat

Summary line

Sprain of right shoulder

Employee and industry

Job description
cook
SOC code
35-2021 — Food Preparation Workers
NAICS code
445110 — Supermarkets
NAICS vintage
2012
Avg employees
225
Total hours worked
403298
EIN
942803364
Establishment ID
406993
Employer case #
19

When (timing detail)

Date of incident
Shift started
7:00
Time of incident
11:00
Filing year
2025
Submitted
25FEB26:19:48:00

More injuries at Berkeley Bowl Main

View Berkeley Bowl Main's full OSHA safety record →

More injuries in this industry (NAICS 445110)

AMARILLO, TX—

WM 4464

ALBUQUERQUE, NM—

WM 3385

More injuries in CA

Rancho Cucamonga, CA—

087-RCDC

Source

Data from OSHA ITA Form 300/301 electronic submissions, filing year 2025. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.