Telegram RegisterThe public register of Telegram
Telegram profile photo for catalog lain > @snowymarts

Channel

catalog lain > @snowymarts

@catalogsnowy

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

106subscribers

-3 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002243795679
TypeChannel
Username@catalogsnowy
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live7 October 2026
Measurements held3
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/catalogsnowy

Topic

Software piracy — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 7 October 2026 and assigned it the closest of 31 fixed categories, at 71% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

106109107.58 August 2026 — 109 subscribers9 August 2026 — 109 subscribers7 October 2026 — 106 subscribers8 August 20267 October 2026
3 measurements spanning 60 days, net -3. 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 106–109 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 02:41106-3
9 Aug 2026, 07:31109no change
8 Aug 2026, 01:30109first reading

Engagement

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

Reaction mix

6 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6100.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 2 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 27 December 2024 to 17 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.

Recent posts

2 May 2026, 12:41 UTC165 viewsread 9 August 2026

🌟 𝐇eartopia 𝐃iamond 🌟20 ʜᴅ :: 8.000 🌟60 ʜᴅ :: 20.000 🌟300 ʜᴅ :: 80.000 🌟680 ʜᴅ :: 165.000 🌟1.280 ʜᴅ :: 295.000 🌟1.980 ʜᴅ :: 450.000 🌟3.280 ʜᴅ :: 735.000 🌟6.480 ʜᴅ :: 1.450.000 NOTE : • VILOG ONLY! • 100% AMAN dan TRUSTED! • avail tumpuk, contoh : 300hd + 1280hd! • proses 1 - 10 menit, max 30 menit - 1j! • kesalahan mengisi format seperti USN & PW BUKAN TANGGUNG JAWAB ADMIN! 在 𝐅𝐨𝐫𝐦𝐚𝐭 𝐇𝐞𝐚𝐫𝐭𝐨𝐩𝐢𝐚 ❥㆐Username ꠩ ❥㆐Pa…

2 May 2026, 01:57 UTC129 viewsread 9 August 2026

➕ 𝐔pfoll 𝐑oblox 100 f᥆ᥣᥣ : 9.000 200 f᥆ᥣᥣ : 18.000 300 f᥆ᥣᥣ : 27.000 400 f᥆ᥣᥣ : 36.000 500 f᥆ᥣᥣ : 45.000 600 f᥆ᥣᥣ : 54.000 700 f᥆ᥣᥣ : 63.000 800 f᥆ᥣᥣ : 72.000 900 f᥆ᥣᥣ : 81.000 1.000 f᥆ᥣᥣ : 90.000 2.000 f᥆ᥣᥣ : 170.000 3.000 f᥆ᥣᥣ : 250.000 4.000 f᥆ᥣᥣ : 330.000 5.000 f᥆ᥣᥣ : 410.000 ...nominal up tanyakan saja! NOTE : • NO RUSH ORDER! • difollow menggunakan acc kosongan! • dikerjakan secara manual, harap sabar! • no…

15 Aug 2025, 06:56 UTC598 views5 reactionsread 9 August 2026

⬜ 𝐑obux via GAME PAS ( PAYTAX ) 🪙100 ʀᴏʙᴜx :: 16.000 🪙200 ʀᴏʙᴜx :: 30.000 🪙300 ʀᴏʙᴜx :: 45.000 🪙400 ʀᴏʙᴜx :: 58.000 🪙500 ʀᴏʙᴜx :: 70.000 🪙600 ʀᴏʙᴜx :: 85.000 🪙700 ʀᴏʙᴜx :: 96.000 🪙800 ʀᴏʙᴜx :: 110.000 🪙900 ʀᴏʙᴜx :: 123.000 🪙1.000 ʀᴏʙᴜx :: 140.000 ...nominal up tanyakan di roomchat! NOTE : • proses pengiriman 3 - 5 hari! • pastikan nominal gamepass sudah benar dan tidak di private! • kesalahan mengisi format BUKA…

❤5

19 Mar 2025, 03:54 UTC≈1,310 viewsread 9 August 2026

backup @snowymartss karna sekarang ch rawan ke ban, kalian boleh subs ch di atas ya guys buat jaga² aja☺️

19 Jan 2025, 07:50 UTC≈1,650 viewsread 9 August 2026
Photo

🗝️ 𝐑ɑოυɑი 𝐙ᥱ⍴ᥱt᥆ 6.000 / ɑcc 在 𝐅𝐨𝐫𝐦𝐚𝐭 𝐑𝐚𝐦𝐮𝐚𝐧 ᰔ⋆.˚㆐ID zepeto ꠩ ᰔ⋆.˚㆐Password ꠩ ᰔ⋆.˚㆐Slot ke? ꠩ ᰔ⋆.˚㆐Payment ꠩ 🌐 : @queenlily0🔂/ @snowymartsBOT 🔐 : @snowymarts 🛡 : @snowyproffs

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

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.

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

“catalog lain > @snowymarts” (@catalogsnowy), 106 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/catalogsnowy.

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.