usvsiran.com

March 5, 2026

What usvsiran.com is today (and why it looks different than you’d expect)

If you type usvsiran.com right now, you don’t land on a typical “US vs Iran” explainer page. It redirects into a live OSINT-style dashboard branded bamqam and explicitly described as “bamqam (formerly: usvsiran.com).”

The interface is basically a control panel sitting on top of a map. It’s organized around “Operational Controls,” map layers, and data feeds. You’ll see things like aircraft tracking, ship tracking, satellites, NOTAM, OSINT, UKMTO, plus overlays for GPS jamming, fires, and other signals.

The important thing: the site frames itself as informational and entertainment-oriented, with a very strong legal posture around misuse, especially commercial reuse.

The core idea: a “theater operations” map built from multiple live-ish feeds

The dashboard is titled “CENTCOM Theater Operations Map | US vs Iran Force Tracker” and it’s oriented around the Middle East / CENTCOM context.

From the UI labels, it’s trying to do a few things at once:

• Show a tactical-ish picture (bases, ports, runways, “SAM rings,” routes/lanes).
• Pull in live or near-live movement data: aircraft (ADS-B), vessels (AIS), satellites.
• Add “situational awareness” layers that aren’t strictly military units: GPS jamming overlays, fire detections, disasters, NOTAM, plus a general OSINT feed and UKMTO references (shipping incident reporting context).
• Provide time filtering (“1H…7D”) and a “Time Machine” to look back over longer windows.

That mix matters because it tells you what the site is really good for: pattern-spotting and monitoring, not definitive “this unit is here and doing X” claims. Movement feeds (ADS-B/AIS) are inherently incomplete, spoofable, and uneven across regions. Overlay layers (fires, jamming) can be useful hints, but they’re still hints. The site actually acknowledges this pretty bluntly in its Terms (more on that below).

What you can and can’t trust on a site like this

A dashboard like this is only as solid as its inputs and its rules for stitching them together. usvsiran.com/bamqam shows its mindset in two places: the UI and the Terms.

On the UI side, it advertises frequent monitoring (“Monitoring every 1m”) and multiple “live” categories like ADS-B Live and Live AIS. That suggests the experience is designed for constant refresh: people watching for changes, not reading a static report.

On the Terms side, the operator basically says: do not rely on this for anything consequential, and assume errors/outdated info happen. It’s “as is,” may be inaccurate, and shouldn’t drive safety or operational decisions.

So if you’re using it responsibly, the mental model should be:

• Treat markers as candidates, not confirmations.
• Cross-check anything important with primary reporting, official statements, or multiple independent OSINT sources.
• Expect false negatives (stuff missing) more often than false positives (stuff that never existed), but both can happen.

The site’s own posture lines up with this: it’s not positioning itself as an authoritative intelligence product, even if it looks like one.

The “community platform” angle and why the legal language is so heavy

The Terms describe bamqam/usvsiran.com as a community platform, including user-submitted reports/annotations (“User Content”). That’s a big deal because community OSINT platforms tend to attract both careful contributors and people who want to push narratives.

Two parts stand out:

1. User content licensing/public-domain release. The Terms say contributing users release their submissions into the public domain (to the fullest extent permitted) and grant broad rights to the operator.
2. Misinformation is explicitly prohibited, especially around military operations and conflict zones, and there’s an enforcement model (warnings, removal, suspensions/bans).

That combination is basically: “we want contributions, but we want maximum control and minimal liability.” Whether you like that or not, it’s consistent with someone trying to run a high-risk, high-drama topic site without getting dragged into endless ownership disputes or legal threats.

Also, there’s a very direct restriction: personal, non-commercial use only, and it explicitly calls out commercial embedding, screenshots for media, paid reports, redistribution, and even using content to train ML/AI systems commercially without written consent.

If you’re a journalist, analyst, or someone building a product, that’s not a small footnote. It changes what you can safely do with what you see on the screen.

Privacy and data handling: what the policy tells you as a user

The Privacy Policy is relatively specific for a small independent tool.

It says it may collect typical account/profile info (email via auth provider, display name/callsign, bio, country, social links) and anything you submit as content. It also lists automatic collection like IP address, device/browser, pages visited, timestamps, referrers, and approximate location derived from IP.

A few practical implications:

• If you contribute, your display name, avatar, and country may be public alongside contributions.
• It mentions Supabase for storage/auth, and notes data may be stored outside Israel.
• It states it doesn’t sell personal info, but it may share data for operations, legal requests, protecting rights/safety, and DMCA processes.

If you’re in a sensitive role (researcher, military-adjacent, activist, etc.), you’d want to think carefully before posting anything identifying or linking accounts. The platform is about conflict monitoring; that topic tends to attract scrutiny.

How people tend to use a site like this (the good uses and the risky uses)

Based on what’s visible in the UI (layers + time controls + feeds), there are a few realistic use patterns:

• Event monitoring: “Something happened, show me nearby air/sea traffic patterns + any jamming/fires signals.”
• Context building: “Where are major bases/ports/runways in the region, and what routes matter?”
• Retrospective checking: using the time filters and “Time Machine” conceptually to sanity-check whether a pattern was abnormal.

Risky uses are the ones the Terms are basically yelling about:

• Treating it as verified intelligence.
• Publishing screenshots commercially (including monetized newsletters/paid research) without permission.
• Using it to guide safety decisions in real time.

A grounded way to use it is as a “lead generator.” If you see a cluster of signals, you take that as a prompt to verify elsewhere.

What makes usvsiran.com/bamqam distinct from generic conflict maps

There are plenty of conflict maps online, but this one is unusually explicit about being a force-tracker flavored dashboard with operational overlays and live transport feeds, not just a pinboard of incidents.

Two other distinct bits:

• It’s tied to a named operator (Nehemia Gershuni-Aylho) in the UI and legal docs, not an anonymous “team.”
• It links out to a live stream presence (“live on Twitch”), which suggests it’s meant to be watched, toured, and interacted with continuously.

That combination (serious-looking tooling + creator-driven distribution + strict terms) is a pretty specific kind of internet product: it wants wide attention, but controlled reuse.

Key takeaways

• usvsiran.com currently redirects to bamqam, described as “formerly: usvsiran.com,” and presents a live map dashboard.
• The UI emphasizes layered monitoring: aircraft (ADS-B), vessels (AIS), satellites, NOTAM, OSINT/UKMTO, plus overlays like GPS jamming and fires.
• The Terms are strict: personal/non-commercial only, and it explicitly restricts commercial screenshots/embedding/redistribution and some AI/ML training uses without written consent.
• The site disclaims accuracy and warns against relying on it for safety, operations, or consequential decisions.
• Privacy policy highlights public display of some profile fields with contributions and use of Supabase for storage/auth.

FAQ

Is usvsiran.com an official government tracker?

No. The legal documents identify an individual operator and frame the service as informational/entertainment, with strong disclaimers about accuracy and reliance.

Why does it say bamqam instead of usvsiran?

The Terms and Privacy Policy explicitly state “bamqam (formerly: usvsiran.com).”

Can I use screenshots of the map in a paid report or a monetized newsletter?

The Terms explicitly prohibit commercial use, including screenshots/recordings for media publications and paid reports, without prior written consent.

What kind of data does it appear to show?

From the interface labels: map layers for infrastructure and military context, plus data feeds including aircraft tracking (ADS-B), ship tracking (AIS), satellites, NOTAM, OSINT, UKMTO, and overlays like GPS jamming and fires.

If I create an account, what personal info might be collected?

The Privacy Policy lists account/profile details you provide (email via auth provider, display name/callsign, country, social links, content you submit) and automatic data like IP address, device/browser, and usage logs.