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

Beaverton, OR —

OSHA Injury Report: Township-United Building Services, LLC

Injury · Days away from work

At a glance

On , an injury at Township-United Building Services, LLC in 7763 SW Cirrus Drive, Beaverton, OR 97008 resulted in days away from work. Employee was janitor in janitorial services.

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

Where did this happen?

Establishment
Township-United Building Services, LLC
Parent company
Township-United Building Services, LLC
Street
7763 SW Cirrus Drive
City
Beaverton
State
OR
ZIP
97008
On-site location
boiler room

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
16

Before the incident

conducting the boiler blow down.

What happened

Burned right hand while conducting the boiler blow down.

Injury or illness

Burn on right hand

Object or substance involved

boiler

Summary line

Burned right hand while conducting the boiler blow down.

Employee and industry

Job description
Janitor
SOC code
37-2011 — Janitors and Cleaners, Except Maids and Housekeeping Cleaners
NAICS code
561720 — Janitorial services
NAICS vintage
2022
Avg employees
486
Total hours worked
730555
Establishment ID
475331
Employer case #
190108457

When (timing detail)

Date of incident
Shift started
8:00:00.000
Time of incident
8:30:00.000
Filing year
2023
Submitted
23FEB24:16:10:00

More injuries at Township-United Building Services, LLC

View Township-United Building Services, LLC's full OSHA safety record →

More injuries in this industry (NAICS 561720)

More injuries in OR

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.