Telegram RegisterThe public register of Telegram
Telegram profile photo for Codes by Mo 🎶

Channel

Codes by Mo 🎶

@CodesByMo

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

191subscribers

-19 since we began measuring on 30 September 2026

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

Register entry

Telegram ID-1003728869188
TypeChannel
Username@CodesByMo
CreatedBetween 1 February 2026 and 2 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded30 September 2026
Last confirmed live10 November 2026
Measurements held8
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/CodesByMo

Topic

Software piracy — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 20 October 2026 and assigned it the closest of 31 fixed categories, at 38% 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 the other topics.

Growth

191210200.530 September 2026 — 210 subscribers30 September 2026 — 210 subscribers5 October 2026 — 204 subscribers13 October 2026 — 205 subscribers20 October 2026 — 203 subscribers27 October 2026 — 202 subscribers2 November 2026 — 197 subscribers10 November 2026 — 191 subscribers30 September 202610 November 2026
8 measurements spanning 42 days, net -19. 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 188–213 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Nov 2026, 21:57191-6
2 Nov 2026, 23:26197-5
27 Oct 2026, 06:27202-1
20 Oct 2026, 10:14203-2
13 Oct 2026, 23:55205+1
5 Oct 2026, 15:20204-6
30 Sept 2026, 08:22210no change
30 Sept 2026, 07:47210first reading

Engagement

15 posts held, back to 2 June 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 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 15 posts for this entry, the most recent from 17 September 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

13 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 69.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤969.2%
🔥323.1%
😁17.69%

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 15 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 13 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 2 June 2026 to 17 September 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

17 Sept 2026, 07:42 UTC86 views3 reactionsread 30 September 2026
File

Leaked By Credit : @bishalpaswanbot OB55 DONE ✅

❤3

15 Sept 2026, 13:27 UTC87 viewsread 30 September 2026
Photo

https://m.youtube.com/watch?v=zjyFFyX0-ms&feature=youtu.be 💓 See for yourself: Unlock fast and secure internet with Shadowsocks VPN! Enjoy unrestricted browsing and top-notch privacy today. 🔐🌍 | InsideAds.

11 Aug 2026, 13:52 UTC201 viewsread 30 September 2026

https://youtu.be/JKz4aIb4_Qk 🎉 Join in quickly: Have you encountered a financial scam? Join us to share your story and explore recovery options! 🚀💰 | InsideAds

9 Aug 2026, 11:41 UTC190 viewsread 30 September 2026

https://youtu.be/AZrg8XjHPOY pkg update && pkg upgrade -y && pkg install python python-pip openssl libffi binutils -y && pip install --upgrade pip && pip install pycryptodome requests urllib3 cryptography

27 Jun 2026, 10:21 UTC430 viewsread 30 September 2026
Photo

🔥 Premium Code & Tutorial Collection 🔥 📦 Full Access / All Files 😻 ✅ 3952+ Web & SWD (Sketchware) Project Files 📚 Includes: • Topup Projects • Casino Projects • Tournament Systems • App & Web Source Code • PHP Basic Projects • Facebook & IMO Related Tutorials • Sketchware Tutorial Videos • And many more... 💰 Price: 109 BDT / 109 INR 📸 Buyer proof available. 📩 DM to Buy: 🇧🇩 @fgfahim387 🇮🇳 @SPIDEERIO ⚡ Serious bu

20 Jun 2026, 09:41 UTC393 viewsread 30 September 2026
Photo

Do you have a Telegram channel? Are you already monetizing it? 🤔 Try Inside Ad — I’ve already started earning. Here’s the link: https://t.me/InsideAds_bot/open?startapp=r_8040570552

15 Jun 2026, 07:22 UTC305 views1 reactionsread 30 September 2026
Forwarded from @spideerio_yt

}, { "_id": "🏁", "emoji_id": "5411520005386806155" }, { "_id": "⚙️", "emoji_id": "5341715473882955310" }, { "_id": "♾️", "emoji_id": "5021555348780090571" }, { "_id": "🎚️", "emoji_id": "5287686383027114707" }, { "_id": "👍", "emoji_id": "5469770542288478598" }, { "_i…

😁1

8 Jun 2026, 12:19 UTC395 views3 reactionsread 30 September 2026

🚀 OTP Verification API Documentation 📩 Send OTP API Endpoint: https://otp-verification-api-rouge.vercel.app/sms?number=9102091415 ✅ Success Response { "message": "OTP sent successfully", "phone": "9102091415", "status": "success" } --- 🔐 Verify OTP API Endpoint: https://otp-verification-api-rouge.vercel.app/otp?number=9102091415&otp=108792 --- ❌ Invalid / Expired OTP Response { "message": "Invalid OTP…

❤3

8 Jun 2026, 02:47 UTC330 viewsread 30 September 2026
Photo

Kisi ko kuch pta hai kya , mere dost ke phone pe hidden number se call arha aur ab gmail se video call aarha aur mai bta du ye google meet se nhi aarha ye direct phone app pe show ho rha , [email protected] ---> attacker maybe

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

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

“Codes by Mo 🎶” (@CodesByMo), 191 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/CodesByMo.

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.