Telegram RegisterThe public register of Telegram

Channel

A_K_A_N_E♡

@B_Akane

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry

20subscribers

+0 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-1002058853365
TypeChannel
Username@B_Akane
DescriptionПо всем вопросам писать - @Jijika_36
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/B_Akane

Growth

208 August 2026 — 20 subscribers11 August 2026 — 20 subscribers8 August 202611 August 2026
2 measurements spanning 3 days. 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 19–21 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 16:1620no change
8 Aug 2026, 18:5220first reading

Engagement

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

What this channel posts

Photos
208
Videos
1
Links
2

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

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3050.8%
💘1016.9%
custom 5217491649449438910915.3%
🔥58.47%
👍35.08%
🐳23.39%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.

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 13 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 59reactions 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 22 May 2025 to 24 July 2025, 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

24 Jul 2025, 16:36 UTC131 views5 reactionsread 11 August 2026
Photo

Трейдик , скоро ещё один будет:3😍

5

Signed °^°

2 Jun 2025, 08:50 UTC114 viewsread 11 August 2026

Таймлапс потом загружу , когда скачается🐱

Signed °^°

2 Jun 2025, 08:47 UTC111 viewsread 11 August 2026

Смотрим , радуемся , ставим реакции 🤭

Signed °^°

2 Jun 2025, 08:46 UTC103 views12 reactionsread 11 August 2026
Photo

Наконец-то доделала😥 @zero_sector4

custom 52174916494494389108🐳2👍2

Signed °^°

1 Jun 2025, 19:58 UTC74 views1 reactionsread 11 August 2026
Photo

Контент делается🙂

1

Signed °^°

31 May 2025, 14:38 UTC74 views1 reactionsread 11 August 2026

В прошлый раз не добили 20 реакций ,так что, если в этот раз добьёте 15 , то завтра ловилку сделаю🥺

1

Signed °^°

31 May 2025, 14:32 UTC71 viewsread 11 August 2026

Тг качество скушал, вам ничего не оставил😪

Signed °^°

31 May 2025, 14:31 UTC70 views9 reactionsread 11 August 2026
Photo

Осталось оформить покрасивее, и увидите вы её на ауке ;3 Как обычно: если не купят, то вам на лоту закину 🩵

6💘3

Signed °^°

31 May 2025, 05:49 UTC56 views1 reactionsread 11 August 2026

Я вас поняла Ушла смотреть гайды, как записывать таймлапсы🥹

custom 52174916494494389101

Signed °^°

30 May 2025, 18:15 UTC54 viewsread 11 August 2026
Poll

Хоте ли бы видеть таймлапсы?🐱

  1. 👍78%
  2. 🙅‍♂️22%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Signed °^°

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

30 May 2025, 18:15 UTCAnonymous Poll9 voters

Хоте ли бы видеть таймлапсы?🐱

  1. 👍78%
  2. 🙅‍♂️22%

Shares as published. No per-option vote count is published by Telegram, so none is 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 22 May 2025 to 24 July 2025. 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 — 940,310 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

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

“A_K_A_N_E♡” (@B_Akane), 20 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/B_Akane.

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.