Channel
@fvckingjay
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
282subscribers
-10 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001440314600 |
|---|---|
| Type | Channel |
| Username | @fvckingjay |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/fvckingjay |
Personal blog — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 26 Sept 2026, 03:39 | 282 | -2 |
| 12 Sept 2026, 18:15 | 284 | -1 |
| 28 Aug 2026, 19:12 | 285 | -1 |
| 21 Aug 2026, 13:53 | 286 | -2 |
| 14 Aug 2026, 21:53 | 288 | -4 |
| 7 Aug 2026, 01:02 | 292 | no change |
| 7 Aug 2026, 00:41 | 292 | first reading |
20 posts held, back to 1 July 2023 — 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 20 posts for this entry, the most recent from 3 July 2026. An engagement rate over an empty window would be a number about nothing.
моё внимание – это привилегия. моё присутствие – это привилегия. мой ответ – это привилегия. разговаривать со мной, моё хорошее отношение к тебе, я в твоей жизни – это подарок судьбы и невероятное везение.
өртенгенде от қайғы, жаным сені жоқтайды
личный блог
наша 4х летняя история на этом заканчивается, мне было весело с вами.
удалился везде, можете следить тут частичку моей жизни. всех обнял поднял и на прогиб кинул, всем хорошей жизни ребята) приватный блог чона
я с кем угодно, только не с тобой.
неткен шынайысың, тура осылай ұнайсың. көзіңнің қарасымен сау санамды улайсын.
просто подари мне один свой взгляд.
Photo, posted without a caption
көптеген ұйқысыз түндерімнің сен - айысың.
пообещай, что не влюбишься в меня.
Sticker, posted without a caption
Showing the 12 most recent of 20 posts we hold for @fvckingjay. 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.
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.
Named by 2 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.
@fvckingjay named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“блог чона” (@fvckingjay), 282 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/fvckingjay.
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.