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

Roseville, CA —

OSHA Injury Report: Trader Joe's 0080 Roseville

Injury · Other recordable case

At a glance

On , an injury at Trader Joe's 0080 Roseville in 1117 Roseville Square, Roseville, CA 95678 resulted in other recordable case. Employee was crew in grocery Store.

Watch Trader Joe's 0080 Roseville — free Get an email when a new federal OSHA severe-injury report for Trader Joe's 0080 Roseville is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
Trader Joe's 0080 Roseville
Parent company
Trader Joe's
Street
1117 Roseville Square
City
Roseville
State
CA
ZIP
95678
On-site location
Sales Floor

What was the outcome?

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

Before the incident

lifted trash can cover up to access trash bag placed trash bag into inner container and while placing outer part of trash can over the inner part the metal can fell onto toe.

What happened

smashed toe

Injury or illness

Contusion Right Big Toe

Object or substance involved

Trash Can

Summary line

Metal trash can smashed toe.

Employee and industry

Job description
Crew
SOC code
35-3023 — Fast Food and Counter Workers
NAICS code
445110 — Grocery Store
NAICS vintage
2022
Avg employees
142
Total hours worked
183064
EIN
951987958
Establishment ID
323038
Employer case #
4

When (timing detail)

Date of incident
Shift started
14:00:00.000
Time of incident
21:30:00.000
Filing year
2023
Submitted
02MAR24:01:55:00

More injuries at Trader Joe's 0080 Roseville

View Trader Joe's 0080 Roseville'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 2023. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.