Channel
@evelode
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
468subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001246659207 |
|---|---|
| Type | Channel |
| Username | @evelode |
| Created | Between 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 20 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 20 August 2026 |
| On Telegram | t.me/evelode |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 20 Aug 2026, 21:33 | 468 | +1 |
| 14 Aug 2026, 20:07 | 467 | -3 |
| 8 Aug 2026, 04:46 | 470 | no change |
| 7 Aug 2026, 21:05 | 470 | first reading |
20 posts held, back to 9 March 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.
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 12 June 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
7 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 42.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 42.9% | |
| 👍 | 2 | 28.6% | |
| 🔥 | 2 | 28.6% |
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 7 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 7reactions 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 9 March 2026 to 12 June 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Trusted Developer Available for Nextpost and Custom Web Projects I’d like to recommend Damilola (@dologbonjaye) for development work related not only to Nextpost, but also to custom web projects, SaaS platforms, integrations, and general development tasks. Damilola has been part of the Nextpost community for a long time — more than 7 years now — and understands its ecosystem, technical structure, and the real needs…
Signed Sergey Komlev
🚀 @jsonscraper is now live on Uneed! Support us with an upvote or review - it really helps the project grow. 🎁 Bonus for everyone who supports us: https://www.uneed.best/tool/jsonscraper Thanks from @jsonscraper ❤️
🔥1
Signed Sergey Komlev
Introducing Wallet Auto-Renewal Your licenses now renew automatically using your @Evelode wallet - no manual actions required. • automatic renewals • wallet balance tracking • instant email confirmations • fallback to manual renewal anytime
Signed Sergey Komlev
We’ve added Active Accounts Tracking to @Evelode Monitor how close you are to your account limits in real time and get notified before hitting the cap. - live usage tracking - smart notification thresholds - email alerts before limits are reached No sudden stops. Stay in control as you scale.
Signed Sergey Komlev
@Evelode now supports Passkeys A faster, safer way to log in - no passwords needed. • biometric login (Face ID / Touch ID) • device-based authentication • improved security by default Security without friction.
❤1
Signed Sergey Komlev
New Requests Limit Monitoring is live Stay ahead of your API usage with real-time tracking and customizable notification thresholds. • 50% / 75% / 95% / 100% alerts • email notifications • accurate usage insights No more surprises. Full control over your limits. @evelode
Signed Sergey Komlev
We’ve just rolled out Endpoints Analytics on @Evelode. Track usage across every API endpoint in real time, analyze trends over the last 30 days, and identify what actually drives your workload. - per-endpoint stats - detailed usage charts - built for high-scale APIs Stop guessing. Start measuring.
Signed Sergey Komlev
Evelode pinned «Here are some useful Telegram channels and chats if you’re interested in scraping, social media automation, APIs, and developer discussions. 🚀 Scraping & APIs (TikTok / Instagram) @jsonscraper - updates, tools, and insights around TikTok & Instagram scraping…»
We’ve just launched on Product Hunt 🚀 https://www.producthunt.com/products/jsonscraper If you have a minute, your support and honest feedback would mean a lot 🙌 We’re building this for real-world use - and every comment helps us improve.
Signed Sergey Komlev
24h to go 🚀 @jsonscraper is launching on Product Hunt. Unified API for TikTok & Instagram data — fast, reliable, built for scale. Support us 👇 https://www.producthunt.com/products/jsonscraper
👍1
Signed Sergey Komlev
We’ve released a TikTok-focused update expanding scraper API coverage and improving data control. What’s included: - new endpoints for live, stories, playlists, rankings, and search - region parameter added across key TikTok methods - improved searchUser filters - enhanced getUserFeed with more control options - updated Postman collections and response examples This update is aimed at teams running @jsonscraper in …
👍1
Signed Sergey Komlev
Building a TikTok Scraper API in public Follow the journey 👇 Channel: @jsonscraper Chat: @jsonscraperchat X: https://x.com/jsonscraper
Signed Sergey Komlev
Showing the 12 most recent of 20 posts we hold for @evelode. 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 — 937,060 of 1,584,420entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 1 registered channel — 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.
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 20 August 2026 — this entry's latest reading, not the date you are reading this.
“Evelode” (@evelode), 468 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/evelode.
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.