Channel photo updated
![Telegram profile photo for [🍞] Brötchen Fanfiction core](https://cdn.tgregister.com/av/74/74559bf76e399e551af33de2c946ac113ba3b047772c99aa44c03f47370bb2eb.jpg)
Channel
[🍞] Brötchen Fanfiction core
@brotchen_sat
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
129subscribers
+128 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 | -1002637751671 |
|---|---|
| Type | Channel |
| Username | @brotchen_sat |
| Description | Сатурн, женись на мне she/her Фанфики: @brotchen_fanfiction Щп: @brotchen_st Лс: @brotch6n Анон: http://t.me/voprosy?start=5x5wl Тамблер: https://www.tumblr.com/br6tchen?source=share Ао3: https://archiveofourown.org/series/5909821 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 October 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 5 |
| On Telegram | t.me/brotchen_sat |
Topic
Literature — 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 4 October 2026 and assigned it the closest of 31 fixed categories, at 82% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Oct 2026, 06:22 | 129 | no change |
| 4 Oct 2026, 05:36 | 129 | +128 |
| 24 Aug 2026, 14:35 | 1 | -1 |
| 16 Aug 2026, 02:05 | 2 | +1 |
| 7 Aug 2026, 19:08 | 1 | first reading |
Engagement
18 posts held, back to 25 September 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.
- ERR · 30 days
- 41.0%
- avg views ÷ 129 subscribers
- Avg views / post
- 52.9
- 17 posts measured
- Reaction rate
- 17.9%
- reactions ÷ views · ER floor
- Posts in window
- 18
- of 18 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. It is computed over the 14 of 17 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 October 2026 |
|---|---|
| Posts held | 18 (25 September 2026 – 4 October 2026) |
| Views total | 899 |
| Reactions total | 131 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 4 Oct 2026, 06:22 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.
What this channel posts
- Photos
- 745
- Videos
- 40
- Links
- 68
Lifetime counters from Telegram’s own channel header, read 4 October 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
131 reactions across 14 posts, in 14 distinct kinds. The most used accounts for 32.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5472317878801800869 | 43 | 32.8% | |
| custom 5258376933493732311 | 20 | 15.3% | |
| custom 5219721544929941631 | 13 | 9.92% | |
| custom 5431427445091762260 | 12 | 9.16% | |
| 💘 | 9 | 6.87% | |
| custom 5431527126987735293 | 8 | 6.11% | |
| ❤🔥 | 6 | 4.58% | |
| custom 5283094985678292407 | 5 | 3.82% | |
| custom 5300892698792714335 | 4 | 3.05% | |
| 💔 | 4 | 3.05% | |
| 🍓 | 3 | 2.29% | |
| custom 5411303891222427446 | 2 | 1.53% | |
| 💋 | 1 | 0.763% | |
| 💯 | 1 | 0.763% |
Custom emoji. 8 of the rows above are 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 counts beside them are Telegram’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 14 of the 18 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 131 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 25 September 2026 to 4 October 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
Ну ладно вам, накидайте каких-нибудь идей по кому хотите небольшой драббл на кинктябрь ахаха Ладно, простите, меня в последнее время поглотила апатия, поэтому я буквально ничего особо не делаю (кроме учебы). Во всяком случае, арт к главе есть, сама глава на половине. Сейчас вот рисую новую аватарку канала епп🥺
custom 54723178788018008695custom 52583769334937323112custom 54314274450917622602
Ну давайте, пишитеее Кстати, думаю, что сяду сегодня наконец-то за главу. Как будто бы хорошее настроение сегодня🥺
custom 54723178788018008694custom 52583769334937323112custom 53008926987927143352custom 54113038912224274461custom 54315271269877352931
Вы бы хотели какой-нибудь драббл на кинктобер?? Если да, то напишите с кем и как🥺
custom 54314274450917622607💘5❤🔥4🍓2custom 52583769334937323112
Давно не было ИИ слопа❤️🔥❤️❤️ они такие няшы я прям не могу. Только Сириус стал желтым вместо голубого
custom 54315271269877352935❤🔥1🍓1💘1
А поч шприцы на сатурняшку. Вы что, с целусней ее путаете🌟
custom 52197215449299416315custom 52830949856782924075
М-м-мужчина... Сегодня у меня был отвратительный день, но зато вот мэйл!Сатурн ахаха #1917_ау
custom 547231787880180086913custom 52197215449299416316custom 54314274450917622603💋1💯1custom 52583769334937323111custom 54113038912224274461
Это телифон Николай
custom 54723178788018008696custom 52197215449299416312❤🔥1custom 53008926987927143351
Sticker, posted without a caption
custom 52583769334937323113
Спойлер к арту !! Его я уже нарисовала, осталось дописать "Аривидерчи"
custom 54723178788018008697💘3custom 54315271269877352932custom 52583769334937323111custom 53008926987927143351
Video, posted without a caption
custom 54723178788018008695
не обзывайс🤛🤛
Signed 𓂃 ˚𝑇𝑖`𝑟𝑒𝑥𝑖࿔ ֶָ֢˚
Showing the 12 most recent of 18 posts we hold for @brotchen_sat. 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 4 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
[Бонус!] Кто в тексте описывается, как человек со светлыми волосами и испуганными глазами, на красивом лице которого красовались два пятна, одно на лбу, а второе рядом с правым глазом голубого цвета?
- Целус44%
- Ариэль11%
- Оберон39%
- Сатурн6%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
[3/3] Кто произнес фразу "Захлопнись, Уран. Еще раз подобное скажешь, и я сошлю тебя в "Кресты" без разбирательств"?
- Юпитер40%
- Титания35%
- Икс25%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
[2/3] Кто произнес фразу "Скажи спасибо своему „Вайненену“, что чертов трамвай пришел, и я тебя не задушил"?
- Сатурн12%
- Икс65%
- Целус24%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
[1/3] Кто сказал фразу "Николай, привыкнете к этому"?
- Псо12%
- Вайз41%
- Симп24%
- Юпитер24%
Shares as published, totalling 101%. 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 18 most recent posts we hold, published 25 September 2026 to 4 October 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.
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 8 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.
@meawlinanews · 182 postsartist's cf
@artisthomecl · 10,3611 postJUPITER confession/ solarballs
@ipiterf · 1111 postᛖᴙϯѧ!🌿
@minti_artist · 961 postлогово скрепыша.
@moonculttt · 1401 postЗаморожен SolarBalls confessions! 🌍🗣️
@solarballs_Confa · 1,6091 post『🧊URANUS CONFESSION🖌』
@uranuscf · 1601 post» Saturn / Uranus confession «
@UranusSaturn · 611 post
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 4 October 2026 — this entry's latest reading, not the date you are reading this.
“[🍞] Brötchen Fanfiction core” (@brotchen_sat), 129 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/brotchen_sat.
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.