COMPANY RECORD · PHILADELPHIA, PA
Basch Builders — permit history in Philadelphia, PA
Basch Builders appears on 46 Philadelphia permit records from 2021 through 2026. Residential Building accounts for 78.3% of the record. This page describes recorded permits; it is not a live statement of availability, capacity or licensing.
What the permit record shows
In Philadelphia’s public permit data, Basch Builders is primarily recorded for residential building work. The record also contains 10 permits in other categories and 26 named participants on linked project timelines. That makes this page useful for checking past activity and preparing a conversation with the company. It does not tell us how much work the company has today, whether it is taking new jobs, or whether it is the right fit for a particular scope.
Work history
Permit categories
The table shows how the issuing authority classified permits that name Basch Builders. These are permit counts, not revenue, crew size or market share. Small categories remain visible instead of being rounded away.
| Category | Permits | Share |
|---|---|---|
| Residential Building | 36 | 78.3% |
| Building | 8 | 17.4% |
| Zoning | 1 | 2.2% |
| Master Plan | 1 | 2.2% |
Activity by year
The record runs from 2021 to 2026. The yearly counts show when permits were issued. A busy year can contain several permits for one project, so the totals should be read as filing activity rather than a measure of current workload.
| Year | Permits issued |
|---|---|
| 2021 | 11 |
| 2022 | 6 |
| 2023 | 20 |
| 2024 | 5 |
| 2025 | 3 |
| 2026 | 1 |
Names connected to the same projects
What a connection means
A connection means that Basch Builders and another name appear on permits tied to the same resolved project timeline. It is a useful lead for research, but it is not proof of a partnership, a hiring relationship or a current contract. The source does not label every name as a company, so names are shown as published by the authority.
| Name in source | Linked permits | Last seen |
|---|---|---|
| Clear Light Electric Llc | 33 | 2025-04-11 |
| Mk Fire Protection & Supply, Llc | 28 | 2025-04-02 |
| Thomas Uhl | 20 | 2025-01-16 |
| Al-Kaun Co | 17 | 2024-06-25 |
| Radoslaw Zbikowski | 10 | 2023-09-24 |
| Jose Rodriguez | 8 | 2023-07-07 |
| Andrius Ratkevicius Inc | 3 | 2024-06-05 |
| Bradley Otto | 3 | 2025-04-03 |
| Dauria & Son Mechanical Contractors Llc | 2 | 2024-09-30 |
| Tdk Enterprises Inc. / Ark Protective Services | 2 | 2022-12-19 |
| Express Power Inc | 2 | 2025-01-23 |
| Gaceta Plumbing Llc | 2 | 2023-01-31 |
How to use this page
For a contractor, supplier or project team
Use the record to build a shortlist and ask a more specific question. Start with the company’s dominant work category, check how recently it appears in the data, and compare any shared project names with the authority’s original record. If you are looking for current capacity, confirm the scope, schedule, license and insurance directly with the company.
What the history cannot answer
Permit history cannot confirm today’s backlog, prices, crew availability, licensing status, insurance or willingness to take a new job. A quiet period can also mean that work was filed outside this dataset. Historical evidence narrows the search; it does not replace qualification or a direct conversation.
Source and limits
Where the numbers come from
This page uses public Philadelphia L&I permit records available through 2026. Projects Ahead counts distinct permit numbers, groups the displayed trade names, and links records only when the available project fields support the connection. Names are kept as published; the public page does not add directory contacts or make a legal-entity claim.
Verify current details with the Philadelphia public permit source. The methodology explains the data treatment, and the page footer shows the source snapshot date.
Prepared by Projects Ahead from public municipal records. Figures describe historical filings and should be verified before a commercial decision.
Looking for the next opportunity?
A current project match requires a separate signal built from newer source activity and a verified project context. Permit history is the starting point, not a promise of the next job.