Telegram RegisterThe public register of Telegram
Telegram profile photo for Devs Nightmare 💻

Channel

Devs Nightmare 💻

@soldevnightmarebot

On this record: Growth · Engagement · Reactions · Advertising · Posts · Citations · Cite this entry

6,226subscribers

-27 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001785405604
TypeChannel
Username@soldevnightmarebot
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/soldevnightmarebot

Growth

6,2266,2536,239.57 August 2026 — 6,253 subscribers7 August 2026 — 6,251 subscribers11 August 2026 — 6,244 subscribers14 August 2026 — 6,234 subscribers17 August 2026 — 6,226 subscribers7 August 202617 August 2026
5 measurements spanning 10 days, net -27. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 6,222–6,257 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 18:236,226-8
14 Aug 2026, 23:576,234-10
11 Aug 2026, 04:436,244-7
7 Aug 2026, 19:186,251-2
7 Aug 2026, 12:326,253first reading

Engagement

20 posts held, back to 4 March 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 4 December 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

245 reactions across 15 posts, in 19 distinct kinds. The most used accounts for 35.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥8735.5%
5723.3%
🙏3413.9%
👏187.35%
🤡156.12%
👍83.27%
👎52.04%
31.22%
🤔31.22%
🤣31.22%
💯20.816%
🖕20.816%
🤯20.816%
❤‍🔥10.408%
🍌10.408%
💋10.408%
🕊10.408%
🤝10.408%
🥰10.408%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 15 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 245reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 4 March 2025 to 4 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Advertising

Ad load
10.0%
2 of 20 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
3,040
over 1 measured post
Median views · rest
3,690
over 15 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 20 most recent posts we hold, published 4 March 2025 to 4 December 2025. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

4 Dec 2025, 09:02 UTC≈2,760 viewsread 12 August 2026
Photo

🔄REKT Bot Got: Telegram channel snipe feature 🚀 🆕AFK Channels are here! No more forwarding services; you can now buy directly from channels inside REKT bot. Choose your favorite Telegram callers and configure your preferred settings all in one place. Just hit Start > AFK Channels. 📢 Need more channels added? Contact @r3kted

24 Apr 2025, 06:45 UTC≈5,900 views6 reactionsread 12 August 2026

⚠️To report, make suggestions and ask questions you can reach us in our bot group, where we created dedicated topic for checker related stuff: https://t.me/REKTbotChat/23

6

8 Apr 2025, 08:55 UTCviews —

Devs Nightmare 💻 pinned «🚨DevsNightmarePro Update – Cleaner, Faster, Smarter🚨 We’ve refactored the bot. Here’s what’s new: Faster & More Stable Scans: The backend got a proper cleanup. Load handling is now optimized, which means scans run quicker and are less likely to choke under…»

8 Apr 2025, 08:54 UTC≈5,860 views26 reactionsread 12 August 2026

🚨DevsNightmarePro Update – Cleaner, Faster, Smarter🚨 We’ve refactored the bot. Here’s what’s new: Faster & More Stable Scans: The backend got a proper cleanup. Load handling is now optimized, which means scans run quicker and are less likely to choke under pressure. Token Tracking Count: Curious how many people are watching the same token? Now you’ll know. Might help spot early hype… or a bubble. Fixed a Misleadi

🔥15👏63❤‍🔥1👍1

2 Apr 2025, 08:31 UTC≈4,470 views14 reactionsread 12 August 2026

So with more data some tokens have millions of transactions, and when users trying to check these tokens multiple times, we are crashing,especially when bot still scans and user hit same function again and again as bot checks everything on the go,so here is next steps: 1. Deleting database of older than 1 week tokens, so meanwhile at least we should be stable. 2. Refactoring code to make it more efficient(already i

14

27 Mar 2025, 12:36 UTC≈4,220 views11 reactionsread 12 August 2026

DevsNightmarePro just rolled update. PumpSwap is fully onboard now, and we've made some bug fix in PumpFun. Happy hunting on these naughty DEV's 😈

8💯2🍌1

24 Mar 2025, 14:56 UTC≈3,920 views11 reactionsread 12 August 2026

👉 Integrating pumpswap amm currently 😈

👏64🔥1

18 Mar 2025, 15:05 UTC≈3,940 views14 reactionsread 12 August 2026

Bot is back on, missing data for last 1h, other than that migrated old database also. You can start using @DevsNightmareProbot again.

🔥93💋1🤝1

18 Mar 2025, 14:05 UTC≈3,690 views11 reactionsread 12 August 2026

Bot is going off, will be adding bigger disk so we can run 3 months of data without interrupt .

🔥101

16 Mar 2025, 08:59 UTC≈3,440 views7 reactionsread 12 August 2026

We have some issues with our node, bot is working but node went down that's why no info found. Trying to resolve.

👏6🙏1

Showing the 12 most recent of 20 posts we hold for @soldevnightmarebot. 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 — 257,513 of 1,549,376entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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.

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 17 August 2026 — this entry's latest reading, not the date you are reading this.

“Devs Nightmare 💻” (@soldevnightmarebot), 6,226 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/soldevnightmarebot.

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.