Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝐂𝐎𝐃𝐄 𝐑𝐄𝐕𝐈𝐄𝐖𝐒

Channel

𝐂𝐎𝐃𝐄 𝐑𝐄𝐕𝐈𝐄𝐖𝐒

@code_otz

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

77subscribers

-4 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-1003795944449
TypeChannel
Username@code_otz
CreatedBetween 1 February 2026 and 5 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live2 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 2 October 2026
On Telegramt.me/code_otz

Topic

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 28 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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

768379.58 August 2026 — 81 subscribers9 August 2026 — 81 subscribers15 August 2026 — 83 subscribers23 August 2026 — 80 subscribers30 August 2026 — 78 subscribers9 September 2026 — 76 subscribers2 October 2026 — 77 subscribers778 August 20262 October 2026
7 measurements spanning 55 days, net -4. 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 75–84 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 01:4077+1
9 Sept 2026, 05:5776-2
30 Aug 2026, 08:4678-2
23 Aug 2026, 13:4280-3
15 Aug 2026, 08:1883+2
9 Aug 2026, 18:4781no change
8 Aug 2026, 00:1881first reading

Engagement

20 posts held, back to 5 March 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 20 posts for this entry, the most recent from 13 May 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

13 May 2026, 07:54 UTC352 viewsread 9 August 2026
Photo

Спасибо за доверие ❤️ Сумма доверия : 600грн / 1200₽

19 Apr 2026, 11:05 UTC537 viewsread 9 August 2026
Photo

Спасибо за доверие ❤️ Сумма доверия : 16.000грн / 32.000₽

15 Apr 2026, 07:06 UTC542 viewsread 9 August 2026

Купил рандомку, ВЫПАЛ ПИЗДЕЦ ЖИР, советую всем спасибо огромное @mngCODE

14 Apr 2026, 07:12 UTC533 viewsread 9 August 2026
Photo

Спасибо за доверие ❤️ Сумма доверия : 1000грн / 2200₽

7 Apr 2026, 14:59 UTC593 viewsread 9 August 2026
Photo

Спасибо за доверие ❤️ Сумма доверия : 500грн / 1100₽

7 Apr 2026, 11:26 UTC527 viewsread 9 August 2026
Photo

Спасибо за доверие ❤️ Сумма доверия : 300грн / 650)

29 Mar 2026, 20:15 UTC568 viewsread 9 August 2026

Продал бабочку @mngCODE После того как отдал бабочку сразу получил оплату всем советую 💋

25 Mar 2026, 09:27 UTC661 viewsread 9 August 2026
Photo

Спасибо за доверие ❤️ Сумма доверия : 600грн / 1500₽

21 Mar 2026, 10:25 UTC727 viewsread 9 August 2026
Photo

Спасибо за доверие ❤️ Сумма доверия : 2000грн / 4000₽

14 Mar 2026, 21:00 UTC796 viewsread 9 August 2026
Photo

Спасибо за доверие ❤️ Сумма доверия : 2200грн / 4200₽

12 Mar 2026, 20:58 UTC762 viewsread 9 August 2026
Photo

Спасибо за доверие ❤️ Сумма доверия : 600грн / 1500₽

11 Mar 2026, 19:10 UTC727 viewsread 9 August 2026
Photo

Спасибо за доверие ❤️ Сумма доверия : 2000грн / 4300₽

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

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

“𝐂𝐎𝐃𝐄 𝐑𝐄𝐕𝐈𝐄𝐖𝐒” (@code_otz), 77 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/code_otz.

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.