2,042,423Injury reports 130,778Establishments Most recent incident 2025-12-31
Safety Incidents OSHA Severe Injury Reports · 2015–2025

Beverly Hills, CA —

OSHA Injury Report: Nowhere Beverly Hills, LLC

Injury · Days away from work

At a glance

On , an injury at Nowhere Beverly Hills, LLC in 339 N. Beverly Drive, Beverly Hills, CA 90210 resulted in days away from work. Employee was prep Cook in grocery stores.

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

Where did this happen?

Establishment
Nowhere Beverly Hills, LLC
Parent company
Nowhere Beverly Hills, LLC
Street
339 N. Beverly Drive
City
Beverly Hills
State
CA
ZIP
90210
On-site location
Kitchen

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
3
Days restricted or transferred
25

Before the incident

Pulled a tray out of the oven

What happened

Weight on tray caused to lose grip and tray made contact with R forearm

Injury or illness

Burn to R forearm lower arm

Object or substance involved

Tray

Summary line

R forearm 2nd degree burn taking a tray out of the oven

Employee and industry

Job description
Prep Cook
SOC code
35-2021 — Food Preparation Workers
NAICS code
445110 — Grocery stores
NAICS vintage
2012
Avg employees
221
Total hours worked
418861
EIN
872590966
Establishment ID
980449
Employer case #
C-107

When (timing detail)

Date of incident
Shift started
14:00
Time of incident
9:15
Filing year
2025
Submitted
18FEB26:18:47:00

More injuries at Nowhere Beverly Hills, LLC

View Nowhere Beverly Hills, LLC'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.