Telegram RegisterThe public register of Telegram

Channel

تست کده جدید

@Robotcodetest

On this record: Growth · Engagement · What this channel posts · Posts · Polls · Citations · Cite this entry

356subscribers

+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-1003915184020
TypeChannel
Username@Robotcodetest
Descriptionاینجا جدید ترین ربات ها تست میشه
CreatedBetween 1 April 2026 and 29 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/Robotcodetest

Growth

3567 Aug 2026, 19:23 — 356 subscribers8 Aug 2026, 06:45 — 356 subscribers7 Aug 2026, 19:238 Aug 2026, 06:45
2 measurements taken within a single day. 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 355–357 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 06:45356no change
7 Aug 2026, 19:23356first reading

Engagement

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

What this channel posts

Photos
9
Links
105

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

Recent posts

22 Jun 2026, 10:44 UTC61 viewsread 8 August 2026

با هر رفرال 50هزار تومن به کیف پولت اضافه میشه و میتونی سرور دلخواهت رو انتخاب کنی و بگیری هم سرور وایرگارد داره هم سرور ویتوری داره بجنب که تایمش تموم نشه اگه تموم بشه هر رفرال بر میگرده به 10هزار تومن

31 May 2026, 18:38 UTC155 viewsread 8 August 2026

https://t.me/Zero_vpnn_bot?start=ref_8665274985 عالیه 10 رف 20 گیگ

30 May 2026, 13:34 UTC394 viewsread 8 August 2026

عالیه بزنین جدید شارژ کرده هر 1 رفرال 1 استارز

30 May 2026, 13:33 UTC151 viewsread 8 August 2026

https://t.me/tpronetbot?start=8665274985 عالی هر رف 1 استارز

30 May 2026, 12:56 UTC270 viewsread 8 August 2026

5 گیگ 200 هر رف 40 فقط باید دریافت هدیه بزنین تا شارژ شه

30 May 2026, 12:55 UTC135 viewsread 8 August 2026

دوستان بخش زیرمجموعه دریافت هدیه بزنین حتما که40 بده

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

29 May 2026, 21:15 UTCAnonymous Poll20 voters

چالش لایک بده برنده 1 تمن

  1. اره بریم75%
  2. نه45%

The shares total 120%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 29 May 2026 to 22 June 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Mentions

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

“تست کده جدید” (@Robotcodetest), 356 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Robotcodetest.

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.