https://t.me/dysphoriacar/154

Channel
Dysphoria API
@DysphoriaAPI2
On this record: Growth · Engagement · Posts · Citations · Cite this entry
126subscribers
+4 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003847995266 |
|---|---|
| Type | Channel |
| Username | @DysphoriaAPI2 |
| Created | 11 May 2026 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 28 August 2026 |
| On Telegram | t.me/DysphoriaAPI2 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 11:23 | 126 | +1 |
| 14 Aug 2026, 18:37 | 125 | +3 |
| 9 Aug 2026, 03:30 | 122 | no change |
| 8 Aug 2026, 05:33 | 122 | first reading |
Engagement
13 posts held, back to 11 May 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 62.5%
- avg views ÷ 126 subscribers
- Avg views / post
- 78.8
- 4 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 4
- of 13 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 13 (11 May 2026 – 6 August 2026) |
| Views total | 315 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 03:30 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Recent posts
https://t.me/dysphoriacar/151
Please take a moment to read the following announcement: https://t.me/dysphoriacar/149 It contains important information regarding our Discord server and community updates. Also, make sure you have joined our main Telegram channel to receive all future announcements: https://t.me/dysphoriacar
Methods Update A major update has been deployed across the network with multiple method changes, removals, and performance improvements. The following methods have been completely removed: ACK SYN SAMP These methods have been removed due to low usage and have been replaced with newer, improved solutions that provide better stability and performance. CLOUDFUCKER has officially been replaced with HTTP-STORM. This …
API Reminder It's now been over 1 month since the API endpoint change was announced. If you're still using the legacy /api/ endpoint, you must update it to: .st/api/attack?username= The transition period has now ended. Requests sent to the old endpoint will be blocked by Cloudflare and will no longer reach our API. Methods Update An updated methods list has also been posted below. Please refer to the new screen…
Reminder A reminder that the official Dysphoria API pricing is available on our website under "Main Network API". https://dysphorianetwork.st/#pricing If you're interested in API access or have any questions about integration, feel free to contact support. @ppsgod
1 Million Attacks Milestone We've officially surpassed 1,000,000 attacks sent through the Dysphoria API. On June 13, we were sitting at just 300,000 attacks. In only 17 days, we've processed 700,000+ additional attacks, reaching the 1 million milestone. Thank you to everyone who continues to support the service. 20% Discount Promotion (3 Days Only) For the next 3 days, all new purchases are eligible for a discou…
Methods Update ACK-PSH, FTP, and MCJE have been removed due to low usage and replaced with three new methods: SYN SOCKET OVH Details and descriptions for all methods can be found when connecting to the CNC using the methods command. Note: L7 is currently disabled. An update for L7 will be released at a later date. Contact: @ppsgod
The API network has been updated, increasing the available API slots from 40 to 55. The website has been updated to reflect these changes. The attached image shows 50 active slots generating approximately 381.49 Mpps, averaging around 7 Mpps per con. Advertised average output per con: • 30–40 Gbps • 6–10 Mpps Please note that these figures are based on averages collected across many dstats and a wide range of con…
Methods Update RDP and SSH have been removed due to low usage and replaced with three new methods: UDPBYPASS ACK ACK-PSH Details and descriptions for all methods can be found when connecting to the CNC using the methods command. API Changes The /api/ endpoint has been renamed to /api/attack?username= All parameters remain the same; only the endpoint path has changed. The legacy /api/ endpoint will remain active…
The API network has been updated, and the number of slots has been doubled. Each con now averages around 40–50 Gbps, although when all slots are in use, output can occasionally drop to around 35 Gbps at the lower end. This only happens under full usage of the network. The website has been updated to reflect these changes. As you can also see from the attached image, 40 cons achieve approximately 1.48 Tbps of traff…
📡 API Plans API plans can be found here: https://dysphorianetwork.st/#pricing ⚠️ Pricing cannot be posted here. For full details, contact: @ppsgod
Showing the 12 most recent of 13 posts we hold for @DysphoriaAPI2. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank
Citation-graph rank — 77,697 of 1,628,927entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 28 August 2026 — this entry's latest reading, not the date you are reading this.
“Dysphoria API” (@DysphoriaAPI2), 126 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/DysphoriaAPI2.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.