Заряночка будет наверное
❤4🎄2custom 53076468784630533301custom 53773660603768057461

Channel
@abigailcipher
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
90subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001857443892 |
|---|---|
| Type | Channel |
| Username | @abigailcipher |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 14 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 14 October 2026 |
| On Telegram | t.me/abigailcipher |
Art & design — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Oct 2026, 08:55 | 90 | +1 |
| 7 Oct 2026, 13:21 | 89 | -1 |
| 26 Sept 2026, 05:17 | 90 | -1 |
| 29 Aug 2026, 02:27 | 91 | -3 |
| 13 Aug 2026, 16:28 | 94 | +1 |
| 9 Aug 2026, 13:16 | 93 | no change |
| 6 Aug 2026, 02:32 | 93 | first reading |
12 posts held, back to 7 May 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 12 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
153 reactions across 12 posts, in 8 distinct kinds. The most used accounts for 27.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🎄 | 42 | 27.5% | |
| custom 5377366060376805746 | 27 | 17.6% | |
| ❤ | 27 | 17.6% | |
| custom 5235639045916207782 | 21 | 13.7% | |
| custom 5190664175617064980 | 12 | 7.84% | |
| custom 5307646878463053330 | 9 | 5.88% | |
| custom 5309804133161651520 | 8 | 5.23% | |
| custom 5235910457784545213 | 7 | 4.58% |
Custom emoji. 6 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 12 of the 12 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 153 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 7 May 2026 to 8 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.
Заряночка будет наверное
❤4🎄2custom 53076468784630533301custom 53773660603768057461
Вот такая девчулька вышла. Всё-таки я ещё умею рисовать акварелью 🫥
custom 52356390459162077826custom 51906641756170649805🎄2
Начала рисовать, а половина красок уже умерло, надо новые брать 👍
custom 53773660603768057467🎄3
В свободное время постараюсь порисовать акварелькой😎
🎄9custom 53773660603768057463
Недавно порисовала гуашью наш местный парк отдыха 🐸
❤11custom 51906641756170649803custom 53773660603768057463🎄2
Мои деревенские Муси 👩❤️👨
❤8🎄6custom 51906641756170649804
Работаю и рисую, работаю и рисую. Сегодня я устав, но всё равно рисовала 🌟
🎄6custom 53773660603768057466
Рисуюс стадики 💓 Телефон какой то дебил, красит лицо на рисунке розовым
custom 52356390459162077825custom 53076468784630533305🎄2
Просто пытаюсь нарисовать хоть что-то в скетчбуке, а то на планшете уже не хочется. Слишком долго, слишком много нужно делать, а мне не хочется. Хочется пока каких-то быстрых зарисовок. Пока хоть на что-то способна, может потом станет легче.😐
custom 53098041331616515208❤4🎄4
Мой старый котек 👀
custom 523563904591620778210🎄1
Опять наскетчила чёта. На этот раз иллюстрация по книге. Работы много, так что буду не скоро 😪
custom 52359104577845452137🎄3custom 53076468784630533303
Решила напечатать зин по своей маленькой поездке в Екб. Началось всё хорошо, печать ровная, страницы наверстала правильно. А когда уже всё разрезала и начала собирать, то поняла, что ничего не сходится. Компуктер всё перепутал, а я за этим не уследила. Пришлось перепечатывать заново. А после этого вышла другая проблема. Принтер решил, что он хочет печатать страницы с полосками выборочно. 🤪Пришлось уже забить на это и…
custom 53773660603768057467🎄2
Showing the 12 most recent of 12 posts we hold for @abigailcipher. 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.
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.
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.
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 14 October 2026 — this entry's latest reading, not the date you are reading this.
“雲の後ろに | ABIGAILC |” (@abigailcipher), 90 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/abigailcipher.
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.