Photo, posted without a caption
Signed Safedev Calls Owner

Channel
@sa7udev
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
20subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001989492102 |
|---|---|
| Type | Channel |
| Username | @sa7udev |
| Created | Between 1 April 2023 and 30 November 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 14 September 2026 |
| On Telegram | t.me/sa7udev |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 04:18 | 20 | -1 |
| 14 Aug 2026, 01:46 | 21 | -1 |
| 11 Aug 2026, 12:49 | 22 | no change |
| 7 Aug 2026, 12:25 | 22 | first reading |
20 posts held, back to 20 April 2024 — 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 page of 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 9 January 2025. An engagement rate over an empty window would be a number about nothing.
6 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 66.7% | |
| 🔥 | 1 | 16.7% | |
| 🤣 | 1 | 16.7% |
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 6 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 6 reactions 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 20 April 2024 to 9 January 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.
Photo, posted without a caption
Signed Safedev Calls Owner
Sloth on Base 🔵🦥 Telegram : https://t.me/SLOTHONBASE Website : https://based-sloth.com Twitter : https://x.com/sloth_based Introducing $SLOTH, the secret agent of the memecoin universe. Known for his selective actions and lightning-fast strikes 🦥 DYOR/nfa
Signed caesar
Could have really flown... Ahh on to the next
Signed Safedev Calls Owner 🔰
Fck, shit honeypot
🤣1
Signed Safedev Calls Owner 🔰
0x2b5ed661f5393cd8e6a1164c949fc18143E6a916 Sniper bot in the works, aped. 1.3k now, good potential, LP burned.
Signed caesar
Safe Dev Launching on BSC in Few Hours..... Join the Community to follow the Timer. 🚀 SONIC AI ($SONIC) is shaking things up on the BSC network! 🚀 🔥 Born from the spirit of ambition and community, this iconic new token is here on BSC to bring some excitement and bullish vibes to the crypto world. 🔥 💥 Key Features of $SONIC: Total Supply: 1,000,000,000 50% Burned at Launch for a robust start Massive #1000X Pote…
Signed Safedev Calls Owner 🔰
very based team launching here, Safe as it gets.🟩 Very good previous. i'm aping👍🏽 Dogita CEO: 🚀 Join Dogita CEO!🐶💼 💪 Strong leadership 🧠 Smart strategies 🎉 Fun community 💸 Tokenomics - 2% LP - 2% Reflections - 4% Development #DogitaCEO #Crypto #MemeToken 🚀 Invest in Dogita CEO today! https://t.me/DOGITACEO
Signed Safedev Calls Owner 🔰
https://t.me/BNBMAGAInu 🟢 Locked and renounced Launched on weekend, Dev is gonna push it....Still very cheap low mc... Community still quite but will kick off at any point. Grabbed a bag...LFG. CA: 0x1B0429A40f0843FBD7C43f85A9fEb62EebdcE36B
Signed Safedev Calls Owner 🔰
Riding on TRUMP HYPE🟩 They are doing well, community very active Just launched, Holding a bag. Dev ssounds legit https://t.me/TRUMPIUM_BSC CA: 0x1aCf71bB9C1b20971e41543843A944b6C3394b61
Signed Safedev Calls Owner 🔰
https://t.me/ProlificGemsCall A good friend of mine...make sure to join up, alwasy calls good.✅
❤2
Signed cear
Chucked an BSC at $BYBY Arabian $PEPE On BSC. Everything is catching a bid https://t.me/+05ITyRDDquYzMzY0
Signed Rain
Prelaunch [BSC] Launching today in few, seems good I will keep eye’s closely and see how it goes. Tg: https://t.me/HalfAndyBSC Ca: 0x2532325923C1fe590A04964140552f5896124C40 Rate: 🟢 NFA/DYOR
Signed Rain
Showing the 12 most recent of 20 posts we hold for @sa7udev. 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.
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.
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.
@sa7udev named 8 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“Safudev Calls 🔰” (@sa7udev), 20 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/sa7udev.
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.