Telegram RegisterThe public register of Telegram

Channel

Aiko kek

@A1ko0FF

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

387subscribers

+1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1004418934921
TypeChannel
Username@A1ko0FF
CreatedBetween 1 June 2026 and 5 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/A1ko0FF

Growth

386387386.56 Aug 2026, 19:52 — 386 subscribers6 Aug 2026, 20:17 — 386 subscribers7 Aug 2026, 10:13 — 387 subscribers6 Aug 2026, 19:527 Aug 2026, 10:13
3 measurements taken within a single day, net +1. 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 386–387 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 10:13387+1
6 Aug 2026, 20:17386no change
6 Aug 2026, 19:52386first reading

Engagement

17 posts held, back to 5 July 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.

ERR · 30 days
316.3%
avg views ÷ 387 subscribers
Avg views / post
1,220
15 posts measured
Reaction rate
3.71%
reactions ÷ views · ER floor
Posts in window
15
of 17 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held17 (5 July 20265 August 2026)
Views total18,363
Reactions total682
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 20:17 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

708 reactions across 17 posts, in 16 distinct kinds. The most used accounts for 55.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
39355.5%
❤‍🔥12717.9%
💘8311.7%
🔥507.06%
🍓202.82%
👎60.847%
💋50.706%
😇50.706%
🥰50.706%
💊40.565%
🦄40.565%
👾20.282%
🍾10.141%
🎉10.141%
👀10.141%
👍10.141%

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

Measured over the 17 most recent posts we hold, published 5 July 2026 to 5 August 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

5 Aug 2026, 21:25 UTC226 views40 reactionsread 6 August 2026
Photo

Работа над дейт сим идёт полным ходоми и теперь движется в разы быстрее благодаря Май! Огромное спасибо ему за помощь, обязательно подпишитесь на его тгк(кликабельно). А пока ловите небольшой спойлер! ^_^

23🔥8❤‍🔥4💘3🍾1💋1

31 Jul 2026, 21:59 UTC633 views87 reactionsread 6 August 2026
Photo

Скетчик Бьянки >ᴗ<

50🔥21❤‍🔥8💘4🍓2🥰2

29 Jul 2026, 19:58 UTC960 views97 reactionsread 6 August 2026
Photo

Спрайтик Кафки. Ему планируется достаточно много образов, но на малое количество спрайтов (1 образ на 2-4 спрайта). Буду рада, если отправите в комменты свои идеи во что его приодеть!! ^_^

56❤‍🔥21💘14💊4👾1🔥1

27 Jul 2026, 16:49 UTC≈1,180 views95 reactionsread 6 August 2026
Photo

Небольшой спойлер (๑•_•๑)

54❤‍🔥26💘9🦄4👍1🔥1

27 Jul 2026, 11:02 UTC932 views105 reactionsread 6 August 2026

Были выбраны ИнфоАнгел и Кафка! (≧ᗜ≦) Не расстраивайтесь, если вы хотели других персонажей. Как будет возможность, я повторно сделаю игру, но уже с другими героями ‹𝟹

56💘29🍓14👎3❤‍🔥2🎉1

26 Jul 2026, 17:01 UTC≈1,090 views3 reactionsread 6 August 2026
Sticker

Sticker, posted without a caption

😇3

26 Jul 2026, 17:01 UTC≈1,070 views22 reactionsread 6 August 2026

Закрою опрос завтра в 14:00 по мск

16💘4😇2

26 Jul 2026, 16:50 UTC≈1,250 views30 reactionsread 6 August 2026
Poll

>_>

  1. Кафка50%
  2. Лука39%
  3. ИнфоАнгел52%
  4. Аня10%
  5. Оля7%
  6. Кирилл12%
  7. Бьянка7%
  8. Свой вариант в комментариях1%

The shares total 178%, 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.

17🔥5👎3❤‍🔥2💘2🍓1

26 Jul 2026, 16:45 UTC982 views24 reactionsread 6 August 2026

Ребят, мне бы очень хотелось сделать со всеми, но это тогда гаремник на 12 серий. Новелла будет от лица Влада, так что да... давайте 2 персонажа максимум Т_Т Сейчас сделаю голосование

21❤‍🔥2🔥1

26 Jul 2026, 12:27 UTC≈2,540 views52 reactionsread 6 August 2026

Я планирую сделать ФАН игру по кисм на минуток 10-15, скорее всего в формате дейт сима. Каких персонажей вы бы хотели увидеть в игре?

❤‍🔥3016🔥4🍓1💘1

25 Jul 2026, 18:34 UTC≈1,350 views27 reactionsread 6 August 2026

Пишите под этим постом, если нашли баги или ошибки 0_<

17❤‍🔥6💘3🔥1

25 Jul 2026, 17:42 UTC≈1,550 views34 reactionsread 6 August 2026

Ремейк 1 главы!! ^_^

22❤‍🔥5💘3🥰2💋1🔥1

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

26 Jul 2026, 16:50 UTCFinal Results329 voters

>_>

  1. Кафка50%
  2. Лука39%
  3. ИнфоАнгел52%
  4. Аня10%
  5. Оля7%
  6. Кирилл12%
  7. Бьянка7%
  8. Свой вариант в комментариях1%

The shares total 178%, 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 17 most recent posts we hold, published 5 July 2026 to 5 August 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.

Citation-graph rank

Citation-graph rank — 574,630 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 4 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.

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

“Aiko kek” (@A1ko0FF), 387 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/A1ko0FF.

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.