Telegram RegisterThe public register of Telegram

Channel

SANTA COIN πŸŽ… || RENOUNCED || FREE GIFTS 🎁

@SantaCoin_Portal

On this record: Growth Β· Engagement Β· What this channel posts Β· Reactions Β· Posts Β· Citations Β· Handles named that no longer answer Β· Cite this entry

56subscribers

+0 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-1002037387547
TypeChannel
Username@SantaCoin_Portal
CreatedBetween 1 November 2023 and 6 December 2023β€” estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/SantaCoin_Portal

Growth

567 August 2026 β€” 56 subscribers10 August 2026 β€” 56 subscribers7 August 202610 August 2026
2 measurements spanning 3 days. 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 55–57 and does not start at zero.
Measurement log β€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 07:3156no change
7 Aug 2026, 00:1756first reading

Engagement

20 posts held, back to 6 December 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 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 14 December 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
6
Videos
1
Links
28

Lifetime counters from Telegram’s own channel header, read 10 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

160 reactions across 18 posts, in 10 distinct kinds. The most used accounts for 43.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
πŸ”₯6943.1%
❀3018.8%
πŸ‘138.13%
😱138.13%
πŸŽ„116.88%
β˜ƒ85.00%
πŸŽ…53.13%
πŸ‘53.13%
πŸ₯°53.13%
😁10.625%

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 18 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 160reactions 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 December 2023 to 14 December 2023, 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

14 Dec 2023, 14:25 UTC790 views4 reactionsread 10 August 2026

#18 Burn πŸŽ… 5M $SANTA BURNT πŸ”₯ TX: https://bscscan.com/tx/0x85dc6624f7585afa7874ae7cc39be65a57db78f987b18b830bdcb0aab19b0da1 TOTAL BURN - 31.5%! NEW ACCOMPLISHMENT! NEXT GOAL 35%!

πŸ”₯3πŸ‘1

12 Dec 2023, 09:17 UTC839 views6 reactionsread 10 August 2026

#17 Burn πŸŽ… 5M $SANTA BURNT πŸ”₯ TX: https://bscscan.com/tx/0xe4d85e55b3cb79be54593e7ba792cd9e3e71e4c9e01c65b35ca7be1b7ed630d5 TOTAL BURN - 31%! NEW ACCOMPLISHMENT! NEXT GOAL 35%!

πŸ”₯6

11 Dec 2023, 21:57 UTC764 views9 reactionsread 10 August 2026

#16 Burn πŸŽ… 5M $SANTA BURNT πŸ”₯ TX: https://bscscan.com/tx/0x5321fd1712fa144c0747a3a0defd2df16f9233a6ccaaaeb0e7b8b428461a1528 TOTAL BURN - 30.5%! NEW ACCOMPLISHMENT! NEXT GOAL 35%!

πŸ”₯7πŸ‘1😱1

11 Dec 2023, 21:13 UTC566 views6 reactionsread 10 August 2026

πŸ”₯ Total Supply of $SANTA Burned: 30.00%

πŸ”₯5😱1

11 Dec 2023, 21:12 UTC593 viewsread 10 August 2026

#15 Burn πŸŽ… 10M $SANTA BURNT πŸ”₯ TX: https://bscscan.com/tx/0x2aebfacb6ae16f6b26bc743502ae38982842bb94d86427e499db71503d0fe179 TOTAL BURN - 30%! NEW ACCOMPLISHMENT!

11 Dec 2023, 18:47 UTC566 views7 reactionsread 10 August 2026

#14 Burn πŸŽ… 40M $SANTA BURNT πŸ”₯ TX: https://bscscan.com/tx/0xdc309cd2293e6c4717e39f195383aa4c9ca6c6a67442d4b125291ab0376d6912 TOTAL BURN - 29%!

πŸ”₯5❀1πŸ‘1

10 Dec 2023, 20:48 UTC467 views7 reactionsread 10 August 2026

🏦 Total Supply of $SANTA Staked: 20.98%

❀5😁1😱1

10 Dec 2023, 17:23 UTC562 views10 reactionsread 10 August 2026
Photo

Our Dex utility is live!!! You can now Buy and Sell $SANTA easily on our Dex, Which has been listed there already with easeπŸ˜‰ Dex: https://santacoin.dexbuilder.app

πŸ”₯6πŸ‘2😱2

9 Dec 2023, 19:00 UTC602 views13 reactionsread 10 August 2026

#13 Burn πŸŽ… 20M $SANTA BURNT πŸ”₯ TX: https://bscscan.com/tx/0x269c8c3164005d933ea4493c494d95280c50297e5bd0c449c0df88f75312c123 TOTAL BURN - 25%!

πŸ”₯9❀2😱2

8 Dec 2023, 23:38 UTC690 views8 reactionsread 10 August 2026

#12 Burn πŸŽ… 10M $SANTA BURNT πŸ”₯ TX: https://bscscan.com/tx/0x2ce8073fea964eabc20a7de88e3520f586f5bf6a1a121757362fe1db3f1a3213 TOTAL BURN - 23%!

❀8

8 Dec 2023, 09:54 UTC645 views23 reactionsread 10 August 2026

SafeAnalyzer | SANTA COIN | πŸ”΅ | Trends πŸ”ΈBSC: 0x1c021A4624CDd765eecc81BF899E2252A2D2C505 πŸ‘¨β€πŸ’»Owner: ***RENOUNCED*** πŸ’§LP Ratio: 18% in Pancakeswap. πŸ‘₯ Holders: 409 | 18.4%| 3.8%| 2.5%| 2.5% πŸ’²MCap: $5,193 BNB:$234 πŸ’°Liquid: $923 (3.94 BNB) ⚑️Initial: M: $454 | LP: 1.0 BNB | X: 11 πŸ”’LP Lock: 99% for 89 days on Mudra πŸ”–Tax: Buy: 8.0% | Sell: 8.2% πŸ•°Age: 5d - 12h 53m 3s βœ…AUDIT: Skeleto…

πŸŽ„9β˜ƒ5πŸŽ…4πŸ‘2πŸ₯°2πŸ”₯1

8 Dec 2023, 09:26 UTC617 views9 reactionsread 10 August 2026

Eleventh Burn πŸŽ… 10M $SANTA BURNT πŸ”₯ TX: https://bscscan.com/tx/0xd7d637f08d979af4249e4bf231c2e94c0bbabb6a5052dcd70048a6bcbe050607 TOTAL BURN - 22%!

β˜ƒ3πŸ”₯3πŸŽ„2πŸŽ…1

Showing the 12 most recent of 20 posts we hold for @SantaCoin_Portal. 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 β€” 819,117 of 1,176,251entries 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

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.

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

β€œSANTA COIN πŸŽ… || RENOUNCED || FREE GIFTS πŸŽβ€ (@SantaCoin_Portal), 56 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/SantaCoin_Portal.

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.