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-846-8393 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 30 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-846-8393 |
| Phone Number | +12028468393 |
| National Format | (202) 846-8393 |
| 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 | 2028468393 |
| Basic Format | 202-846-8393 |
| NPA (Area Code) | 202 |
| NXX | 846 |
| Rate Center | WSHNGTNZN1 |
| Location | WASHINGTON ZONE 1, DC |
| OCN (Carrier Number) | 6117 |
| Call Type | Unknown Type |
| Number Assignment | Assigned |
| Search |
 |
| state | DC |
| ocn | 812C |
| company | INTRADO COMMUNICATIONS LLC |
| rate_center | WSHNGTNZN1 |
| Location | WASHINGTON ZONE 1, DC |
| use_type | AS |
| assign_date | 01/28/2015 |
| initial_growth | I |
| pooled_code | Y |
| in_service | Yes |
| region | MA |
| state | DC |
| status | AS |
| rate_center | WSHNGTNZN1 |
| Location | WASHINGTON ZONE 1, DC |
| block_effective_date | 07/31/2015 |
| assigned_to | LEVEL 3 COMMUNICATIONS, LLC - DC |
| ocn | 6117 |
| date_assigned | 07/07/2015 |
| region | MA |
| state | DC |
| status | AS |
| rate_center | WSHNGTNZN1 |
| Location | WASHINGTON ZONE 1, DC |
| block_effective_date | 07/31/2015 |
| assigned_to | LEVEL 3 COMMUNICATIONS, LLC - DC |
| ocn | 6117 |
| date_assigned | 07/07/2015 |
| 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️⃣4️⃣6️⃣-8️⃣3️⃣9️⃣3️⃣ [click to copy] |
| Spelled Out | two zero two - eight four six - eight three nine 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-846-8393
Anonymous User from San Antonio, Texas
July 18, 2024 at 5:38 PM
Anonymous User from Jersey City, New Jersey
June 20, 2024 at 11:17 AM
Anonymous User from Valdez, AK
June 11, 2024 at 2:50 PM
Anonymous User from Newmarket, New Hampshire
May 2, 2024 at 9:27 AM
Anonymous User from Highlands, NC
May 1, 2024 at 4:06 PM
Anonymous User from Newmarket, New Hampshire
May 1, 2024 at 1:49 PM
Anonymous User from Honolulu, HI
April 30, 2024 at 7:31 PM
Anonymous User from Gary, IN
April 29, 2024 at 2:36 PM
Anonymous User from Thomasvl, GA
April 25, 2024 at 9:21 AM
Anonymous User from Honolulu, HI
April 17, 2024 at 8:09 PM
Anonymous User from Cambridge, MN
April 10, 2024 at 5:19 PM
Anonymous User from Columbia, South Carolina
March 31, 2024 at 4:48 PM
Anonymous User from Thomasvl, GA
March 28, 2024 at 10:18 AM
Anonymous User from Newmarket, NH
March 27, 2024 at 9:42 AM
Anonymous User from Fairbanks, Alaska
March 26, 2024 at 3:11 AM
Anonymous User from Fairbanks, Alaska
March 23, 2024 at 1:35 AM
Anonymous User from Westfield, Indiana
March 22, 2024 at 10:17 AM
Anonymous User from Kailua-kona, Hawaii
March 21, 2024 at 4:30 PM
Anonymous User from Newmarket, New Hampshire
March 21, 2024 at 3:00 PM
Anonymous User from Columbia, SC
March 20, 2024 at 7:15 PM
Anonymous User from Van Buren, Arkansas
March 20, 2024 at 7:11 PM
Anonymous User from Honolulu, HI
March 18, 2024 at 9:47 PM
Anonymous User from Honolulu, HI
March 14, 2024 at 8:42 PM
Anonymous User from Newmarket, NH
March 14, 2024 at 12:34 PM
Anonymous User from Littleton, Colorado
March 11, 2024 at 8:34 PM