мои тщетные попытки освоить клс
custom 51927870448074943661custom 51951519053402809951custom 51952462357070037331

Channel
@justniccolie
On this record: Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
12subscribers
-1 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003778051801 |
|---|---|
| Type | Channel |
| Username | @justniccolie |
| Created | Between 1 February 2026 and 3 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/justniccolie |
@justniccolie was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 07:57 | 12 | -1 |
| 12 Aug 2026, 02:16 | 13 | no change |
| 9 Aug 2026, 14:31 | 13 | first reading |
17 posts held, back to 3 April 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 17 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
162 reactions across 15 posts, in 8 distinct kinds. The most used accounts for 27.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5192787044807494366 | 45 | 27.8% | |
| custom 5192973197280038999 | 30 | 18.5% | |
| custom 5195246235707003733 | 27 | 16.7% | |
| custom 5195407468779293997 | 16 | 9.88% | |
| custom 5195338706352885988 | 15 | 9.26% | |
| custom 5195151905340280995 | 13 | 8.02% | |
| custom 5192921713507061227 | 12 | 7.41% | |
| custom 5195140502202111420 | 4 | 2.47% |
Custom emoji. Every 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 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 15 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 162 reactions 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 3 April 2026 to 9 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.
мои тщетные попытки освоить клс
custom 51927870448074943661custom 51951519053402809951custom 51952462357070037331
я очень хочу порисовать что-нибудь, но идей нет🥺
custom 51929731972800389993custom 51927870448074943662
решила порисовать что-то кроме геншина, поэтому ловите персонажика из моей книги
custom 51954074687792939974custom 51929731972800389993custom 51951405022021114203
Posted without readable text
а потом
custom 51927870448074943668custom 51929731972800389995custom 51952462357070037335
🥺
custom 51927870448074943668custom 51952462357070037337custom 51929731972800389994custom 51951405022021114201custom 51951519053402809951custom 51954074687792939971
привет, блин, реквестики и тд, че вам нарисовать
custom 51927870448074943664custom 51929731972800389991custom 51952462357070037331
когда-то я была фанаткой доттолюков
custom 51929217135070612275custom 51929731972800389993custom 51953387063528859883
чайники чайники и еще чайники, овер дохуя чайников
custom 51953387063528859885custom 51929217135070612273custom 51951519053402809953
бляяяя все хуйня
custom 51927870448074943666custom 51929217135070612273custom 51952462357070037333
🤩🤩🤩🤩🤩🤩🤩🤩 ◯⃝🤩от теорий про Дилюка - 10 предвестника Фатуи, до теорий про мать-ведьму(а может ангела)
custom 51952462357070037335custom 51951519053402809953custom 51929731972800389992custom 51927870448074943661custom 51929217135070612271
🧷🔤оговорим о символизме? Внушительную лепту в ассоциации к персонажам и их системе взаимоотношений вносит символизм. Зачастую для врагов используется прием противопоставления: они противоположны в характерах, во внешности для получения большей динамичности в сцене. Одним из моих любимых примеров такого приема можно назвать Дилюка и Дотторе из геншина и вот почему....🥹🥹
custom 51927870448074943664custom 51929731972800389994custom 51953387063528859883custom 51954074687792939971
Showing the 12 most recent of 17 posts we hold for @justniccolie. 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.
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.
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.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“₊˚𝔫𝗂𝔠𝔠𝗈𝗅𝔦𝔢₊𖥔” (@justniccolie), 12 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/justniccolie.
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.