Telegram RegisterThe public register of Telegram
Telegram profile photo for Central TikTok ⚡️

Channel

Central TikTok ⚡️

@CentralTikTok

Not marked by Telegram, checked 27 August 2026

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Domains linked from posts · Cite this entry

2,064,972subscribers

+149,108 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

Telegram ID-1003549453501
TypeChannel
Username@CentralTikTok
Description⛓️‍💥ОФИЦИАЛЬНЫЕ ОБНОВЛЕНИЯ МОДА НА ТИК ТОК⛓️‍💥 👤 Сотрудничество: @stepnricci / @dooorassss @trafadv Ad. Managers: @oldpurple • @reklama_nikita • @Diman_zhe_nu • @Spiral_Yuri Поддержка - @Tallalai Official TikTok Stable Mod Updates
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/CentralTikTok

Topic

Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 96% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@CentralTikTok/1551 · this entry18 Aug 2026, 15:23 UTC@tiktokupdatez/418020 Aug 2026, 15:28 UTC1.002 days
@CentralTikTok/1585 · this entry24 Aug 2026, 09:21 UTC@tiktokupdatez/419624 Aug 2026, 09:22 UTC1.00under a minute
@CentralTikTok/1597 · this entry25 Aug 2026, 07:54 UTC@tiktokupdatez/420625 Aug 2026, 07:54 UTC1.00under a minute
@CentralTikTok/1685 · this entry1 Sept 2026, 17:00 UTC@tiktokupdatez/42661 Sept 2026, 17:00 UTC1.00under a minute
@CentralTikTok/1728 · this entry9 Sept 2026, 12:00 UTC@tiktokupdatez/43089 Sept 2026, 12:00 UTC1.00under a minute
@CentralTikTok/1781 · this entry14 Sept 2026, 09:18 UTC@tiktokupdatez/435914 Sept 2026, 09:18 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@tiktokupdatez92 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (65–27)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 22 of the 27 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 230 comparable posts for this entry, running 3 August 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @tiktokupdatez. That is a statement about our reading window, not a claim of authorship.

Views and reactions moved apart

On 7 of the 116 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0024 reactions per view.

Each interval, as we read it — views and reactions before and after
PostOverViewsReactionsExpected
/213124 Oct 2026, 20:00 UTC4 days358,000 → 416,000at least +57,000686 → 714at most +29+136.1
/213225 Oct 2026, 08:01 UTC4 days414,000 → 481,000at least +66,000899 → 931at most +33+157.6
/213325 Oct 2026, 19:11 UTC4 days418,000 → 494,000at least +75,000701 → 739at most +39+179.1
/214726 Oct 2026, 05:04 UTC30 minutes147,000 → 174,000at least +26,000237 → 250at most +14+62.1
/22356 Nov 2026, 12:00 UTC31 minutes32,400 → 38,500at least +6,000116 → 118at most +3+14.3
/226410 Nov 2026, 16:09 UTC30 minutes44,600 → 52,300at least +7,60087 → 90at most +4+18.1
/230316 Nov 2026, 17:16 UTC35 minutes37,900 → 45,400at least +7,40079 → 82at most +4+17.7

Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).

What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.

Recorded under the keys clone_source · view_reaction_decoupling, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

1,906,3622,139,9272,023,144.52,064,9727 August 202616 November 2026
66 measurements spanning 101 days, net +149,108. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,871,327–2,174,962 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
16 Nov 2026, 17:152,064,972-7,894
13 Nov 2026, 10:182,072,866-5,045
10 Nov 2026, 23:212,077,911-3,988
9 Nov 2026, 11:102,081,899-3,150
7 Nov 2026, 23:482,085,049-1,382
6 Nov 2026, 18:382,086,431-1,915
5 Nov 2026, 19:272,088,346-2,748
4 Nov 2026, 16:172,091,094-2,057
3 Nov 2026, 18:192,093,151-2,391
2 Nov 2026, 18:242,095,542-2,262
1 Nov 2026, 21:412,097,804-3,162
31 Oct 2026, 20:572,100,966-3,366
31 Oct 2026, 00:062,104,332-2,587
29 Oct 2026, 22:402,106,919-2,925
28 Oct 2026, 21:392,109,844-4,006
27 Oct 2026, 21:362,113,850-1,838
27 Oct 2026, 00:182,115,688+279
25 Oct 2026, 21:142,115,409-1,874
24 Oct 2026, 19:512,117,283-1,412
23 Oct 2026, 19:592,118,695first reading

Engagement

736 posts held, back to 3 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 219 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
10.0%
avg views ÷ 2,064,972 subscribers
Avg views / post
207,000
204 posts measured
Reaction rate
0.296%
reactions ÷ views · ER floor
Posts in window
204
of 736 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 203 of 204 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held736 (3 August 2026 – 17 November 2026)
Views total42,212,921
Reactions total124,763
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 14:00 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
430
Videos
348
Links
885

Lifetime counters from Telegram’s own channel header, read 17 November 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.

Video runtime
20m 28s
Average length
14s

Measured directly from 85 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.

View velocity

How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.

Computed from 202 of this channel’s own posts over the last 30 days: across 95 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 25 hours of being posted; a typical post has already reached 19.1% of its 24-hour view count within the first hour, and 56.5% within the first six; the median 24-hour reach across those posts is 136,000 views — 6.59% of this channel’s own subscriber count (90th percentile 377,200).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/231017 Nov 2026, 12:00 UTC429 minutes – 2.0 hours old35,600 views ~179 reactions60 minutes: 23,100still climbing at last readingnot yet at 24h41 minutesprovisional — final view count still climbing
/230917 Nov 2026, 11:30 UTC15 minutes – 5 minutes old4,050 views ~9 reactionsno checkpoint reading yetnot yet at 24hnot measurable yet
/230817 Nov 2026, 11:00 UTC7under a minute – 3.0 hours old42,800 views ~210 reactions60 minutes: 21,842 interp. → 3.0 hours: 42,800still climbing at last readingnot yet at 24h58 minutesprovisional — final view count still climbing
/230717 Nov 2026, 08:03 UTC1212 minutes – 6.0 hours old66,900 views ~325 reactions60 minutes: 20,599 interp. → 3.0 hours: 39,600 → 6.0 hours: 66,900still climbing at last readingnot yet at 24h2.2 hoursprovisional — final view count still climbing
/230616 Nov 2026, 19:17 UTC227 minutes – 12 hours old61,500 views ~686 reactions60 minutes: 19,203 interp. → 3.0 hours: 29,390 interp. → 6.0 hours: 36,201 interp. → 12 hours: 61,500still climbing at last readingnot yet at 24h3.6 hoursprovisional — final view count still climbing
/230516 Nov 2026, 18:35 UTC3615 minutes – 19 hours old103,000 views ~255 reactions60 minutes: 24,872 interp. → 3.0 hours: 38,900 → 6.0 hours: 45,700 → 12 hours: 67,500still climbing at last readingnot yet at 24h8.1 hoursprovisional — final view count still climbing
/230416 Nov 2026, 17:46 UTC130 minutes – 30 minutes old16,200 views ~37 reactionsno checkpoint reading yetnot yet at 24hnot measurable yet
/230316 Nov 2026, 17:16 UTC3829 minutes – 21 hours old106,000 views ~152 reactions60 minutes: 28,400 → 3.0 hours: 51,244 interp. → 6.0 hours: 59,200 → 12 hours: 74,900still climbing at last readingnot yet at 24h3.4 hoursprovisional — final view count still climbing

Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.

Reaction mix

844,780 reactions across 734 posts, in 12 distinct kinds. The most used accounts for 61.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤516,75461.2%
🤪64,3367.62%
👾41,5014.91%
🔥40,3574.78%
👍36,7674.35%
🤗25,0132.96%
🎉22,8992.71%
🆒21,8572.59%
🙏21,1272.50%
👏20,8152.46%
🏆19,9802.37%
🤝13,3741.58%

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 734 of the 736 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 844,780 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 736 most recent posts we hold, published 3 August 2026 to 17 November 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.

Telegram Stars

Stars received
15,438
across the posts below
Posts paid on
495
of 736 we hold a reading for · 67%
Most on one post
833
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @CentralTikTok. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 736 most recent posts we hold for this entry, published 3 August 2026 to 17 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Advertising

Ad load
0.136%
1 of 736 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
387,000
over 1 measured post
Median views · rest
278,000
over 735 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzqvL9ZNK112 August 202612 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 736 most recent posts we hold, published 3 August 2026 to 17 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 6 of 204 posts held from the last 30 days (2.94%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

17 Nov 2026, 12:00 UTC≈35,600 views179 reactionsread 17 November 2026
Video

Мы с другом на первом уроке😴 📲 Наш МАХ

❤132👍28🤪10🤗7👾2

17 Nov 2026, 11:30 UTC≈12,800 views32 reactionsread 17 November 2026

⭐️ Все забрали звёзды? ⭐️

❤21🤪7👍3🔥1

17 Nov 2026, 11:00 UTC≈42,800 views210 reactions3 Starsread 17 November 2026

Posted without readable text

❤150🤪27🆒10🙏9👍8🎉3👾3

17 Nov 2026, 08:03 UTC≈66,900 views325 reactionsread 17 November 2026
Video

Как же он вкусно ест🤤 📲 Наш MAX

❤240👍40🤪29🔥5👾4🎉3🤗3🆒1

16 Nov 2026, 19:17 UTC≈61,500 views686 reactions36 Starsread 17 November 2026
Photo

🎁Розыгрыш х100 Telegram Premium🎁 🎁условие: ⭐️ Поставить реакцию любую ⭐️ Нажать кнопку «УЧАСТВОВАТЬ» 🎁 Всем удачи 🍀

❤472👾82🎉51👍23🤪14🔥12👏11🏆10

16 Nov 2026, 18:35 UTC≈103,000 views255 reactionsread 17 November 2026
Photo

Ето я, радостный и полный позитива, думаю о своем светлом будущем🫠 📲 Наш МАХ

🎉133❤87👍13👾9🔥7🏆3🤪3

16 Nov 2026, 17:46 UTC≈16,200 views37 reactionsread 16 November 2026

💥Забирай до 11000⭐️ в @RubUP

🤪20❤8👾5👏4

16 Nov 2026, 17:16 UTC≈106,000 views152 reactionsread 17 November 2026
Video

🎁 Мне выпал подарок Toy Bear за 4970 ⭐️ (5100₽) с бесплатного спина в RubUP. Заходи и крути бесплатный спин в RubUP

❤97🤪27👾10👏8👍5🙏3🏆2

16 Nov 2026, 16:22 UTC≈10,900 views82 reactions1 Starread 16 November 2026

67 - участнику дам кольцо 💍

❤50👍12🤪8👏4👾3🏆2🤗1🙏1

16 Nov 2026, 16:01 UTC≈22,700 views277 reactions9 Starsread 16 November 2026
Photo

🎁1⃣2️⃣3⃣👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻👻 🧸1000 мишек бесплатно! 🧸 1-1000 местам по 1 мишке 🧸 для участия: ✅подписка на @maisonkeli ✅ поставить любую реакцию! 🍀Всем удачи!

❤178👍38🤪28🎉9👾9🤝4🙏4🏆3

16 Nov 2026, 14:35 UTC≈23,600 views27 reactionsread 16 November 2026

🎰1000₽ за старт от казино🎰 🎰1000₽ за старт от казино🎰 🎰1000₽ за старт от казино🎰

👍14❤7👾5🤪1

16 Nov 2026, 08:02 UTC≈142,000 views666 reactions13 Starsread 17 November 2026
Photo

Как чувствуют себя трехдневные макарошки на дне кастрюли, в холодильнике😂 📲 Наш МАХ

❤523🤪68👍32🔥18🤗6🏆5👾4🎉3

Showing the 12 most recent of 736 posts we hold for @CentralTikTok. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@CentralTikTok edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
26 August 2026
Most recent edit
23 October 2026

Posts recorded as deleted after publishing

We recorded 17 posts on @CentralTikTok as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
7 August 2026
Most recent seen missing
27 September 2026
Median time before seen missing
37 hours
Seen missing in the last 30 days
0

Forward network

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 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.

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.

Domains linked from posts

4 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

max.ru14 posts · 3 August 2026 – 7 August 2026 · example post
fylio.com5 posts · 3 August 2026 – 3 August 2026 · example post
apps.apple.comregistrable domain: apple.com1 post · 3 August 2026 – 3 August 2026 · example post
play.google.comregistrable domain: google.com1 post · 3 August 2026 – 3 August 2026 · example post

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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“Central TikTok ⚡️” (@CentralTikTok), 2,064,972 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/CentralTikTok.

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.