Telegram RegisterThe public register of Telegram
Telegram profile photo for ๐ŸŒ SAIFU SNIPER v1| $SAIFU

Channel

๐ŸŒ SAIFU SNIPER v1| $SAIFU

@saifusniper

On this record: Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Posts ยท Citations ยท Cite this entry

13subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register ยท movement among entries of Under 1,000.

Register entry

Telegram ID-1001940027461
TypeChannel
Username@saifusniper
Descriptiont.me/saifucoin ๐Ÿšง BEWARE OF RUGS.๐Ÿšง
CreatedBetween 1 April 2023 and 6 June 2023 โ€” estimated from Telegramโ€™s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live18 September 2026
Measurements held3
On Telegramt.me/saifusniper

Growth

131413.57 August 2026 โ€” 14 subscribers8 August 2026 โ€” 13 subscribers12 August 2026 โ€” 13 subscribers7 August 202612 August 2026
3 measurements spanning 5 days, net -1. 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 13โ€“14 and does not start at zero.
Measurement log โ€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 02:4513no change
8 Aug 2026, 08:4113-1
7 Aug 2026, 09:4214first reading

Engagement

20 posts held, back to 6 June 2023 โ€” 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 2 June 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
2
Links
31

Lifetime counters from Telegramโ€™s own channel header, read 12 August 2026 โ€” not the date at the top of this page, which is when the subscriber count was last read. Below Telegramโ€™s rounding threshold, so these counts are exact.

Reaction mix

2 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
๐Ÿ”ฅ2100.0%

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 1 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 2 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 6 June 2023 to 2 June 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.

Recent posts

2 Jun 2025, 20:15 UTCviews โ€”

The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 19 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

20 Jul 2023, 00:54 UTC64 views2 reactionsread 12 August 2026

๐Ÿšจ๐Ÿšจ๐Ÿšจ๐Ÿšจ BRB

๐Ÿ”ฅ2

22 Jun 2023, 09:55 UTC75 viewsread 12 August 2026

๐Ÿ‘€ FIGMA | WETH New ๐Ÿฆ„ Uniswap Pair Created! 0x0CF53f356d15e20c6560fF2273fB9071fECCd136 Figments Club (FIGMA) Wrapped Ether (WETH)

21 Jun 2023, 22:43 UTC56 viewsread 12 August 2026

๐Ÿ‘€ Zorg | WETH New ๐Ÿฆ„ Uniswap Pair Created! 0x3D96a02C1a34948EB0649698baac962f89373BbF Zorg Coin (Zorg) Wrapped Ether (WETH)

19 Jun 2023, 21:57 UTC47 viewsread 12 August 2026

๐Ÿ‘€ PP | WETH New ๐Ÿฆ„ Uniswap Pair Created! 0x2f720700cc2090790D62851d79074D78686a7882 Print The Planet (PP) Wrapped Ether (WETH)

8 Jun 2023, 00:08 UTC42 viewsread 12 August 2026

๐Ÿ‘€ HARAM | WETH New ๐Ÿฆ„ Uniswap Pair Created! 0x534099D1704B6B00aE34C8C55B14590DeE57449E HARAM (HARAM) Wrapped Ether (WETH)

8 Jun 2023, 00:01 UTC32 viewsread 12 August 2026

๐Ÿ‘€ COPIUM | WETH New ๐Ÿฆ„ Uniswap Pair Created! 0x0094CD108AA566bECdAffDC989D16A2B9961B0b1 Copium (COPIUM) Wrapped Ether (WETH)

6 Jun 2023, 06:24 UTC29 viewsread 12 August 2026

๐Ÿ‘€ BYE | WETH New ๐Ÿฆ„ Uniswap Pair Created! 0x60eFb2C0605345fbFBa1a87c1ce40F67BF572EF0 Byenance (BYE) Wrapped Ether (WETH)

6 Jun 2023, 06:23 UTC21 viewsread 12 August 2026

๐Ÿ‘€ CAMO | WETH New ๐Ÿฆ„ Uniswap Pair Created! 0x0B6Ba3DDF35f451802d34a7730f28528c9Dc9208 Camo Cash (CAMO) Wrapped Ether (WETH)

6 Jun 2023, 06:21 UTC13 viewsread 12 August 2026

๐Ÿ‘€ FPOT | WETH New ๐Ÿฆ„ Uniswap Pair Created! 0x909203DA62C9108A1d7d20A104123e25Df15bda6 flowerpot (FPOT) Wrapped Ether (WETH)

Showing the 12 most recent of 20 posts we hold for @saifusniper. 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.

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 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.

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 12 August 2026 โ€” this entry's latest reading, not the date you are reading this.

โ€œ๐ŸŒ SAIFU SNIPER v1| $SAIFUโ€ (@saifusniper), 13 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/saifusniper.

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.