4EB3C7476C710B9826420DFC0E51EE81
โค1

Channel
@freecodefreecode
On this record: Topic ยท Growth ยท Engagement ยท Reactions ยท Posts ยท Cite this entry
2,886subscribers
-964 since we began measuring on 7 August 2026
Risers and fallers across the register ยท movement among entries of 1,000โ3,162.
| Telegram ID | -1002467393821 |
|---|---|
| Type | Channel |
| Username | @freecodefreecode |
| Created | Between 1 September 2024 and 31 March 2025 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/freecodefreecode |
Other / unclassifiable โ 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 20:58 | 2,886 | -57 |
| 4 Oct 2026, 22:00 | 2,943 | -83 |
| 25 Sept 2026, 13:40 | 3,026 | -77 |
| 17 Sept 2026, 08:38 | 3,103 | -32 |
| 13 Sept 2026, 10:39 | 3,135 | -58 |
| 9 Sept 2026, 19:37 | 3,193 | -113 |
| 4 Sept 2026, 09:01 | 3,306 | -82 |
| 31 Aug 2026, 12:17 | 3,388 | -66 |
| 28 Aug 2026, 13:17 | 3,454 | -67 |
| 25 Aug 2026, 16:25 | 3,521 | -64 |
| 22 Aug 2026, 15:57 | 3,585 | -71 |
| 18 Aug 2026, 22:36 | 3,656 | -52 |
| 15 Aug 2026, 15:18 | 3,708 | -64 |
| 11 Aug 2026, 16:47 | 3,772 | -70 |
| 8 Aug 2026, 07:42 | 3,842 | -8 |
| 7 Aug 2026, 18:32 | 3,850 | no change |
| 7 Aug 2026, 18:29 | 3,850 | first reading |
20 posts held, back to 25 May 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 2 pages 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 30 July 2026. An engagement rate over an empty window would be a number about nothing.
32 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 78.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 25 | 78.1% | |
| ๐ | 2 | 6.25% | |
| ๐ฅ | 2 | 6.25% | |
| ๐ฅฐ | 2 | 6.25% | |
| ๐ | 1 | 3.13% |
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 12 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 32 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 25 May 2026 to 30 July 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.
4EB3C7476C710B9826420DFC0E51EE81
โค1
GIVE ME FULL REACTION๐๐ฅ GIFT CODE IS READY๐
New game caming soon guys โบ๏ธ
โค4๐ฅ1๐ฅฐ1
DO YOU WANT SOME GIFT CODE AGAIN?????
โค4
JAI Club โน20+โน20+โน20+โน20+ Free Codes Coming GiftCode Timing : 05 :15 PM
๐2๐ฅฐ1
ARE YOU READY FOR GIFT CODE ๐๐
๐๐๐ ๐๐๐๐ : E2975471DEACCCC65A1EBE7D70E3346D 1577F8322DEEF241A70ADB3DAF9EBDEA 93F9AF5299587BC759BF7C641D6B267C
jalwa 5 20/20rs C0733C55A87C96D87013C315E6781B49 4D6DB68A87F4AEED5CA033654569415E D13FAAA6AE0A5A08B691CB33BE76E3E4 E58856304C4815CEBB7356BBF4F2E0FD C9659D10DF7257F497314570A046A27B
ok win 5 20/20rs FE948893642020A489B3B3B18488F254 4D360C80DE551B34B831C8FFDDC048A5 A37F13590CF0A7936457F60CEBDA5B60 8151B8EC3A03C9ABD29C852F44C17644 0F937E98D45C848C5BCA38B5B487BFBB
4EBC5AAE7C3F8DB6A205CE60A86EA225
โค1
Jai club code ready ๐
33FDB7169DAF4BF31FC48721FD9F58A1 472E0AF3D701470A9AD79DFEB3D25819 D1341985AB9193FEDC8889818EC9AC04
โค2
Showing the 12 most recent of 20 posts we hold for @freecodefreecode. 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.
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 11 October 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐ง๐ฅ๐ฒ ๐ฌ๐จ๐ฎ๐ซ ๐ฌ๐ก๐จ๐ซ๐ญโ (@freecodefreecode), 2,886 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/freecodefreecode.
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.