SHIMMED INC

Landlord profile

Filed as SHIMMED INC · taxpayer 32076439259 · on the county rolls as SHIMMED INC · mail to 519 BUNDY SAN ANTONIO TX 78212Matched to a Texas filing

$125,000Market value

1Properties

760Sq ft living area

≈1Units estimated from floor area

The unit figure is the only estimate in that row: floor area divided by 900 square feet, so it is the third figure restated

Portfolio totals

1parcels on the rolls

1 of them are inside the registry lookup scope

≈1units, estimated

Floor area divided by 900 sq ft, not a count

$125,000total market value

County roll value across all 1 parcels

$125,000median parcel value

The middle parcel, which a total hides

County spread: Bexar 1
ZIPs: 78220
Parcels whose tax bill leaves Texas: 0 of 1
Parcels flagged owner-occupied: 0 of 1
Most recent purchase date on the roll: 19907
Earliest purchase date on the roll: 19907

Source: 1 county appraisal rolls · roll year 2025 to 2026 · purchase dates are the roll's own recent-purchase field and are not reliable deed dates

Download this portfolio as CSV

The Texas business filing behind this name

Filing we matched: SHIMMED INC
Name we searched: SHIMMED INC
Taxpayer number: 32076439259
Right to transact business: FRANCHISE TAX INVOLUNTARILY ENDED
Secretary of State status: INACTIVE
Effective registration: 2020-10-26
State of formation: TX
Texas SOS file number: 0803809322
Registered agent: WILLIAMS TAX FINANCIAL SERVICES INC
Filing mailing address: 13430 PALATINE HL SAN ANTONIO TX 78253

Source: Texas Comptroller franchise tax registry · matched on the owner name as printed on the roll · 1 registry rows carry this owner

Every property on the rolls under this owner

1 parcels held by this owner, with size, age, acquisition date, and market value
Parcel ID	Address	County	Market value ↓	Sq ft	Built	Acquired
000000462153	519 BUNDY ST SAN ANTONIO 78220	bexar	$125,000	760	1972	19907
1 properties			$125,000	760

Values are the county market value on the roll, not a sale price · roll year 2025 to 2026

Companies linked to this one

Shared officer

The same person is named on both filings. This is the strongest link here, and the one worth naming out loud

Shared mailing address

Both filings collect mail at the same address. Suggestive, and worth a second look, but shared suites happen

Shared registered agent

Both hired the same filing service. Weakest line on the diagram, drawn faint on purpose: these firms sign for thousands of unrelated companies

This shows one entity and what sits up to two links away from it. Every line is labelled with the reason for it, because the reason is the claim

How to read the end of a chain

A chain can end three ways, and the difference matters. Two of them are answers. One of them is a gap in what we know, and it is drawn as a gap so you never mistake it for an answer

Matched

The name on the roll lines up with a Texas business filing. We show both names side by side so you can reject a bad match yourself

25,455 owners of the 71,735 inside the coverage rules, 35.5% so far

No record

We searched and Texas has no business registration under this name. That is a finding, not a miss: plenty of rentals are held by a person or an out-of-state entity that never registered here. The line stops on a hard bar because the search finished

37,870 owners so far

No answer

No usable answer came back for this name. Almost all of these are lookups the registry rejected outright, which is our query failing, not Texas reporting that nothing is filed. That claim is the middle column, and this is not it. We do not know either way here, so the line trails off dashed and open

8,410 owners in scope: rejected lookup or never queried

One more case borrows that same dashed ending: a parcel outside the coverage rules. The registry was never asked about it, on purpose, so the chain is a gap here too, and the page names the rule that put it outside instead of implying an answer is on its way. 147,384 of the 2,117,593 parcels on the rolls are inside the rules

11.7%

of the 71,735 owners inside the coverage rules have no registry answer. The scrape has finished, so these are not owners waiting in a queue: almost all of them are lookups the registry rejected. Read them as unknown, never as unregistered