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-813-1600 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 120 public complaint records.
Carrier or assignee data points to LEVEL 3 COMMUNICATIONS, LLC - DC 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-813-1600 |
| Phone Number | +12028131600 |
| National Format | (202) 813-1600 |
| Country Code | US |
| Caller Name | No public caller label found. |
| Caller Type | |
| Carrier Name | LEVEL 3 COMMUNICATIONS, LLC - DC |
| Phone Type | |
| Apple iMessage Status | Not Registered |
| Raw Number | 2028131600 |
| Basic Format | 202-813-1600 |
| NPA (Area Code) | 202 |
| NXX | 813 |
| Rate Center | WSHNGTNZN1 |
| Location | WASHINGTON ZONE 1, DC |
| OCN (Carrier Number) | 6117 |
| Call Type | Unknown Type |
| Number Assignment | Assigned |
| Search |
 |
| state | DC |
| ocn | 7529 |
| company | TELEPORT COMMUNICATIONS AMERICA, LLC - DC |
| rate_center | WSHNGTNZN1 |
| Location | WASHINGTON ZONE 1, DC |
| use_type | AS |
| assign_date | 02/14/2012 |
| 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 | 07/22/2013 |
| assigned_to | LEVEL 3 COMMUNICATIONS, LLC - DC |
| ocn | 6117 |
| date_assigned | 06/04/2013 |
| region | MA |
| state | DC |
| status | AS |
| rate_center | WSHNGTNZN1 |
| Location | WASHINGTON ZONE 1, DC |
| block_effective_date | 07/22/2013 |
| assigned_to | LEVEL 3 COMMUNICATIONS, LLC - DC |
| ocn | 6117 |
| date_assigned | 06/04/2013 |
| 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️⃣-8️⃣1️⃣3️⃣-1️⃣6️⃣0️⃣0️⃣ [click to copy] |
| Spelled Out | two zero two - eight one three - one six zero zero [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-813-1600
Anonymous User from North Andover, Massachusetts
April 15, 2026 at 9:06 PM
Anonymous User from Lompoc, California
March 10, 2026 at 9:09 PM
Anonymous User from Longview, WA
February 25, 2026 at 2:25 AM
Anonymous User from Longview, WA
February 21, 2026 at 4:54 AM
Anonymous User from Longview, WA
February 16, 2026 at 4:28 PM
Anonymous User from Longview, WA
February 10, 2026 at 4:37 PM
Anonymous User from Longview, WA
February 4, 2026 at 9:35 AM
Anonymous User from Montague, Massachusetts
December 15, 2025 at 5:53 PM
Anonymous User from Montague, Massachusetts
December 14, 2025 at 3:05 AM
Anonymous User from Montague, Massachusetts
December 13, 2025 at 12:13 AM
Anonymous User from Moraga, California
December 10, 2025 at 2:42 PM
Anonymous User from Moraga, California
December 10, 2025 at 2:37 PM
Anonymous User from Seattle, WA
December 3, 2025 at 7:19 PM
Anonymous User from Montague, Massachusetts
November 27, 2025 at 2:26 PM
Anonymous User from Montague, Massachusetts
November 27, 2025 at 2:25 PM
Anonymous User from North Falmouth, Massachusetts
November 26, 2025 at 6:55 PM
Anonymous User from Montague, Massachusetts
November 25, 2025 at 4:51 AM
Anonymous User from Montague, Massachusetts
November 25, 2025 at 4:46 AM
Anonymous User from Seattle, WA
November 21, 2025 at 6:04 PM
Anonymous User from Montague, Massachusetts
November 18, 2025 at 7:17 PM
Anonymous User from Montague, Massachusetts
September 19, 2025 at 2:18 PM
Anonymous User from Montague, Massachusetts
September 19, 2025 at 2:15 PM
Anonymous User from Montague, Massachusetts
August 28, 2025 at 2:45 PM
Anonymous User from Montague, Massachusetts
August 28, 2025 at 2:42 PM
Anonymous User from Montague, Massachusetts
August 18, 2025 at 11:04 AM
Anonymous User from Montague, Massachusetts
August 13, 2025 at 9:33 PM
Anonymous User from Durham, Connecticut
August 7, 2025 at 4:16 PM
Anonymous User from Nashua, NH
February 12, 2025 at 5:45 PM
Anonymous User from Seattle, WA
July 18, 2024 at 9:15 PM
Anonymous User from Seattle, WA
February 24, 2024 at 8:19 PM
Anonymous User from Renton, WA
January 10, 2024 at 1:14 AM
Anonymous User from Seattle, WA
December 4, 2020 at 2:19 AM
Anonymous User from Decatur, IL
April 1, 2016 at 3:22 PM
Anonymous User from Tucson, AZ
January 4, 2016 at 5:30 PM