Paste raw digits, a formatted phone number, an area code, an NPA-NXX block, or a short code. US and Canada phone lookups route automatically, and international iMessage checks are available separately.
Server-rendered context for this exact phone page based on public records, reports, search interest, and routing data already stored on phone.gd.
202-640-3413 does not currently have a confirmed public business label on phone.gd, but it remains an active research target because complaint records, anonymous reports, or verified on-site searches continue to surface it.
Current page signals include 10 public complaint records.
Carrier or assignee data points to OMNIPOINT COMMUNICATIONS CAP OPERATIONS, LLC and the rate center is WSHNGTNZN1 (WASHINGTON ZONE 1, DC).
The rows below combine cached caller-intelligence data, NANPA assignment records, public business matches, and phone.gd lookup context.
| Label | Value |
|---|---|
| Input Number | 202-640-3413 |
| Phone Number | +12026403413 |
| National Format | (202) 640-3413 |
| Country Code | US |
| Caller Name | No public caller label found. |
| Caller Type | |
| Carrier Name | OMNIPOINT COMMUNICATIONS CAP OPERATIONS, LLC |
| Phone Type | |
| Apple iMessage Status | Not Registered |
| Raw Number | 2026403413 |
| Basic Format | 202-640-3413 |
| NPA (Area Code) | 202 |
| NXX | 640 |
| Rate Center | WSHNGTNZN1 |
| Location | WASHINGTON ZONE 1, DC |
| SMS/MMS Email Gateways | 2026403413@omnipoint.com 2026403413@omnipoint.com SMS/MMS gateways may be invalid (i.e. the number has been ported or purchased by another carrier) |
| OCN (Carrier Number) | 6855 |
| Call Type | Unknown Type |
| Number Assignment | Assigned |
| Search |
 |
| state | DC |
| ocn | 6855 |
| company | OMNIPOINT COMMUNICATIONS CAP OPERATIONS, LLC |
| rate_center | WSHNGTNZN1 |
| Location | WASHINGTON ZONE 1, DC |
| use_type | AS |
| assign_date | 05/18/2006 |
| initial_growth | G |
| pooled_code | Y |
| in_service | Yes |
| region | MA |
| state | DC |
| status | AS |
| rate_center | WSHNGTNZN1 |
| Location | WASHINGTON ZONE 1, DC |
| block_effective_date | 08/17/2007 |
| assigned_to | OMNIPOINT COMMUNICATIONS CAP OPERATIONS, LLC |
| ocn | 6855 |
| date_assigned | 07/19/2007 |
| region | MA |
| state | DC |
| status | AS |
| rate_center | WSHNGTNZN1 |
| Location | WASHINGTON ZONE 1, DC |
| block_effective_date | 08/17/2007 |
| assigned_to | OMNIPOINT COMMUNICATIONS CAP OPERATIONS, LLC |
| ocn | 6855 |
| date_assigned | 07/19/2007 |
| Bold | 𝟐𝟎𝟐-𝟔𝟒𝟎-𝟑𝟒𝟏𝟑 [click to copy] |
| Full-Width | ２０２-６４０-３４１３ [click to copy] |
| Superscript | ²⁰²-⁶⁴⁰-³⁴¹³ [click to copy] |
| Subscript | ₂₀₂-₆₄₀-₃₄₁₃ [click to copy] |
| Enclosed Alphanumerics | ②⓪②-⑥④⓪-③④①③ [click to copy] |
| Mathematical Bold | 𝟮𝟬𝟮-𝟲𝟰𝟬-𝟯𝟰𝟭𝟯 [click to copy] |
| Mathematical Italic | 𝟤𝟢𝟤-𝟨𝟦𝟢-𝟥𝟦𝟣𝟥 [click to copy] |
| Mathematical Sans-Serif | 𝟸𝟶𝟸-𝟼𝟺𝟶-𝟹𝟺𝟷𝟹 [click to copy] |
| Emoji | 2️⃣0️⃣2️⃣-6️⃣4️⃣0️⃣-3️⃣4️⃣1️⃣3️⃣ [click to copy] |
| Spelled Out | two zero two - six four zero - three four one three [click to copy] |
Using these number formats when publishing your phone number online can help reduce spam calls/texts by making it harder for scammers to copy your number
Submit an anonymous report
Choose the report type that best matches this number, then optionally add a short note about what happened. Your city and state may be shown publicly, but your IP address is not displayed on the page.
Report a spam or fraud caller
Answer a few quick questions and this page will point you to the right official complaint flow, plus carrier-specific reporting options where available.
Step 1
What happened?
Choose the option that best matches this phone number.
Step 2
How did it reach you?
The FCC and carrier advice changes slightly for calls versus texts.
Step 3
Did they ask for money or sensitive information?
This helps decide whether the FTC should be part of the next step.
Step 4
Which carrier do you use?
Carrier tools help get the number flagged or blocked inside that network.
Latest community reports for 202-640-3413
Anonymous User from Alexandria, VA
March 28, 2016 at 2:57 PM
Anonymous User from Burke, VA
January 15, 2016 at 7:31 PM
Anonymous User from Alpine, TX
January 14, 2016 at 10:11 PM
Anonymous User from Detroit, MI
January 13, 2016 at 9:34 PM
Anonymous User from Manassas, VA
January 13, 2016 at 6:10 PM
Anonymous User from Jacksonville, FL
January 13, 2016 at 5:53 PM