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

Beverly Hills, CA —

OSHA Injury Report: Nowhere Beverly Hills, LLC

Injury · Other recordable case

At a glance

On , an injury at Nowhere Beverly Hills, LLC in 339 N. Beverly Drive, Beverly Hills, CA 90210 resulted in other recordable case. Employee was cafe Clerk 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
Cafe

What was the outcome?

Outcome
Other recordable case (code 4)
Type
Injury (code 1)

Before the incident

Got skin irritation allergic reaction on both hands

What happened

Unsure if the hand sanitizer exposure caused skin irritation

Injury or illness

Dermatitis hands both hand

Object or substance involved

Unknown

Summary line

Hands allergic contact dermatitis got skin irritation on both hands sanitizer exposure caused it

Employee and industry

Job description
Cafe Clerk
SOC code
41-2031 — Retail Salespersons
NAICS code
445110 — Grocery stores
NAICS vintage
2012
Avg employees
221
Total hours worked
418861
EIN
872590966
Establishment ID
980449
Employer case #
C-407

When (timing detail)

Date of incident
Shift started
14:00
Time of incident
17:00
Filing year
2025
Submitted
18FEB26:19:56: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.