👼🪇: как же шейный позвонок кормит
custom 53753728605440308125custom 54383317338691100381
Signed notnyashks [⚫🎪|👼🪇]

Channel
@jaybobcf
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
160subscribers
+0 since we began measuring on 11 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003994865853 |
|---|---|
| Type | Channel |
| Username | @jaybobcf |
| Created | Between 1 April 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/jaybobcf |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 07:22 | 160 | no change |
| 11 Sept 2026, 06:47 | 160 | first reading |
15 posts held, back to 27 August 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 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 13 of 15 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 September 2026 |
|---|---|
| Posts held | 15 (27 August 2026 – 10 September 2026) |
| Views total | 1,472 |
| Reactions total | 140 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Sept 2026, 07: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.
Lifetime counters from Telegram’s own channel header, read 11 September 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.
Measured directly from 3 videos 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.
140 reactions across 13 posts, in 17 distinct kinds. The most used accounts for 21.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5472201768655954117 | 30 | 21.4% | |
| custom 5440753498423600401 | 25 | 17.9% | |
| custom 5375372860544030812 | 22 | 15.7% | |
| custom 5438331733869110038 | 12 | 8.57% | |
| ❤🔥 | 12 | 8.57% | |
| 💋 | 7 | 5.00% | |
| custom 5397761769143836649 | 6 | 4.29% | |
| 🙏 | 6 | 4.29% | |
| ❤ | 5 | 3.57% | |
| 💯 | 3 | 2.14% | |
| 😭 | 3 | 2.14% | |
| custom 5474347444122718690 | 2 | 1.43% | |
| 🌭 | 2 | 1.43% | |
| 💘 | 2 | 1.43% | |
| 🍌 | 1 | 0.714% | |
| 🐳 | 1 | 0.714% | |
| 😁 | 1 | 0.714% |
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 13 of the 15 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 140 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 27 August 2026 to 10 September 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 53753728605440308125custom 54383317338691100381
Signed notnyashks [⚫🎪|👼🪇]
А ты попробуй 4 часа постримить
💋6custom 54407534984236004012custom 54722017686559541171
Signed notnyashks [⚫🎪|👼🪇]
У Джея есть дислексия?
The shares total 129%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Signed notnyashks [⚫🎪|👼🪇]
Photo, posted without a caption
custom 547220176865595411713💯3💘2😁1
Signed notnyashks [⚫🎪|👼🪇]
ТВ/КВ НСФВ 👼🪇: Мужик сказал - мужик сделал Creator - - #Дейли ][ @Jaybobtake_bot
❤🔥9🌭2custom 54383317338691100382custom 54407534984236004012❤1🙏1
Signed notnyashks [⚫🎪|👼🪇]
👼🪇: Ну чё как у вас первое сентября Creator - - #Дейли ][ @Jaybobtake_bot
custom 547220176865595411713custom 53977617691438366495custom 54407534984236004014❤2❤🔥1🐳1
Signed notnyashks [⚫🎪|👼🪇]
👼🪇: это слишком ахуенное видео ребята
custom 53753728605440308124custom 54407534984236004011
Signed notnyashks [⚫🎪|👼🪇]
Импотенция в честь того чтобы проважить последний день спокойной жизни От всей души спасибо за звёзды
custom 54407534984236004017🙏1custom 53753728605440308121custom 54383317338691100381
Signed notnyashks [⚫🎪|👼🪇]
Джейбоб порно я найду если Бонзо победит пожалуйста попересылайте куда можете
custom 54383317338691100387
Signed notnyashks [⚫🎪|👼🪇]
Posted without readable text
❤2😭2💋1
Signed notnyashks [⚫🎪|👼🪇]
Ребята подсобите проголосуйтк за Бонзо я умоляю
😭1
Signed notnyashks [⚫🎪|👼🪇]
👻 :: оно довоняло и до нашего фандома тоже я не удержалась
custom 54407534984236004019🙏3❤🔥2custom 54743474441227186902🍌1custom 54383317338691100381
Signed notnyashks [⚫🎪|👼🪇]
Showing the 12 most recent of 15 posts we hold for @jaybobcf. 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.
The 2 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.
У Джея есть дислексия?
The shares total 129%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
ЕСЛИ я создам чат для общения вы захотите там быть общаться и вся хуйня
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 15 most recent posts we hold, published 27 August 2026 to 10 September 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.
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 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Jaybob | Daily + Confession” (@jaybobcf), 160 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/jaybobcf.
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.