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 · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Domains linked from posts · Cite this entry

2,061,968subscribers

+146,104 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 / @dooorass @trafadv Ad. Managers: @oldpurple • @reklama_nikita • @Diman_zhe_nu • @Spiral_Yuri 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 live19 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 19 September 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 why it has no browse page of its own yet.

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 word for word on 1 other registered channel. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@tiktokupdatez/40453 Aug 2026, 02:01 UTC@CentralTikTok/1422 · this entry3 Aug 2026, 02:03 UTC1.003 minutes
@tiktokupdatez/40463 Aug 2026, 02:01 UTC@CentralTikTok/1423 · this entry3 Aug 2026, 02:03 UTC1.003 minutes
@tiktokupdatez/40473 Aug 2026, 02:01 UTC@CentralTikTok/1424 · this entry3 Aug 2026, 02:03 UTC1.003 minutes
@tiktokupdatez/40483 Aug 2026, 02:01 UTC@CentralTikTok/1425 · this entry3 Aug 2026, 02:03 UTC1.003 minutes
@tiktokupdatez/40493 Aug 2026, 02:01 UTC@CentralTikTok/1426 · this entry3 Aug 2026, 02:03 UTC1.003 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@tiktokupdatez5 (5/5 hand-verifiable sample passed)1.003 minutes@tiktokupdatez (50)

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. None of the 5 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 9 comparable posts for this entry, running 3 August 2026 to 7 August 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).

Across the whole group of 2, the earliest publisher we hold is @tiktokupdatez. That is a statement about our reading window, not a claim of authorship.

Views and reactions moved apart

On 15 of the 126 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.0028 reactions per view.

Each interval, as we read it — views and reactions before and after
PostOverViewsReactionsExpected
/163930 Aug 2026, 08:04 UTC30 minutes143,000171,000at least +27,000665674at most +10+76.8
/163930 Aug 2026, 08:04 UTC30 minutes171,000203,000at least +31,000674694at most +21+88.1
/163930 Aug 2026, 08:04 UTC33 minutes203,000241,000at least +37,000694705at most +12+105.2
/163930 Aug 2026, 08:04 UTC30 minutes241,000282,000at least +40,000705721at most +17+113.7
/163930 Aug 2026, 08:04 UTC36 minutes282,000334,000at least +51,000721736at most +16+145.0
/176112 Sept 2026, 19:20 UTC35 minutes156,000194,000at least +37,000793805at most +13+105.2
/176112 Sept 2026, 19:20 UTC34 minutes194,000242,000at least +47,000805817at most +13+133.6
/176112 Sept 2026, 19:20 UTC33 minutes242,000298,000at least +55,000817828at most +12+156.4
/176112 Sept 2026, 19:20 UTC31 minutes298,000354,000at least +55,000828843at most +16+156.4
/176112 Sept 2026, 19:20 UTC37 minutes354,000415,000at least +60,000843863at most +21+170.6
/176213 Sept 2026, 08:01 UTC35 minutes127,000169,000at least +41,000866892at most +27+116.6
/176213 Sept 2026, 08:01 UTC34 minutes169,000225,000at least +55,000892911at most +20+156.4
/176213 Sept 2026, 08:01 UTC33 minutes225,000288,000at least +62,000911930at most +20+176.3
/176213 Sept 2026, 08:01 UTC31 minutes288,000354,000at least +65,000930961at most +32+184.8
/176213 Sept 2026, 08:01 UTC37 minutes354,000421,000at least +66,000961991at most +31+187.6
/164430 Aug 2026, 19:05 UTC30 minutes72,300104,000at least +30,700470484at most +15+87.3
/164430 Aug 2026, 19:05 UTC30 minutes104,000141,000at least +36,000484504at most +21+102.3
/164430 Aug 2026, 19:05 UTC30 minutes184,000229,000at least +44,000533560at most +28+125.1
/164430 Aug 2026, 19:05 UTC36 minutes229,000285,000at least +55,000560590at most +31+156.4
/163829 Aug 2026, 20:03 UTC30 minutes165,000191,000at least +25,000870878at most +9+71.1
/163829 Aug 2026, 20:03 UTC33 minutes219,000254,000at least +34,000887898at most +12+96.7
/163829 Aug 2026, 20:03 UTC36 minutes291,000337,000at least +45,000908920at most +13+127.9
/176313 Sept 2026, 20:03 UTC34 minutes96,900160,000at least +62,100549588at most +40+176.5
/176313 Sept 2026, 20:03 UTC37 minutes308,000384,000at least +75,000710759at most +50+213.2
/158724 Aug 2026, 09:21 UTC34 minutes73,50093,200at least +19,600129135at most +7+55.7
/160526 Aug 2026, 15:31 UTC30 minutes53,60062,700at least +9,0007984at most +6+25.6
/165931 Aug 2026, 07:55 UTC37 minutes165,000223,000at least +57,000271305at most +35+162.0
/166831 Aug 2026, 12:30 UTC39 minutes146,000176,000at least +29,000274283at most +10+82.4

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_copy · view_reaction_decoupling, last confirmed 22 September 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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,065,3361,985,8497 August 2026 — 1,915,864 subscribers7 August 2026 — 1,915,016 subscribers8 August 2026 — 1,914,254 subscribers9 August 2026 — 1,913,143 subscribers10 August 2026 — 1,911,459 subscribers11 August 2026 — 1,910,691 subscribers12 August 2026 — 1,910,003 subscribers14 August 2026 — 1,908,707 subscribers15 August 2026 — 1,907,631 subscribers16 August 2026 — 1,906,362 subscribers17 August 2026 — 1,961,081 subscribers18 August 2026 — 1,967,682 subscribers19 August 2026 — 1,966,893 subscribers20 August 2026 — 1,964,026 subscribers22 August 2026 — 1,962,681 subscribers24 August 2026 — 1,961,154 subscribers25 August 2026 — 1,959,164 subscribers26 August 2026 — 1,958,421 subscribers27 August 2026 — 1,957,392 subscribers28 August 2026 — 1,955,671 subscribers29 August 2026 — 1,954,272 subscribers30 August 2026 — 1,953,386 subscribers31 August 2026 — 1,997,833 subscribers1 September 2026 — 2,019,112 subscribers2 September 2026 — 2,018,882 subscribers3 September 2026 — 2,017,900 subscribers6 September 2026 — 2,016,382 subscribers9 September 2026 — 2,012,729 subscribers11 September 2026 — 2,008,662 subscribers13 September 2026 — 2,007,069 subscribers15 September 2026 — 2,065,336 subscribers16 September 2026 — 2,064,582 subscribers19 September 2026 — 2,061,968 subscribers2,061,9687 August 202619 September 2026
33 measurements spanning 43 days, net +146,104. 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,882,516–2,089,182 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
19 Sept 2026, 11:202,061,968-2,614
16 Sept 2026, 23:412,064,582-754
15 Sept 2026, 03:382,065,336+58,267
13 Sept 2026, 15:562,007,069-1,593
11 Sept 2026, 20:592,008,662-4,067
9 Sept 2026, 12:002,012,729-3,653
6 Sept 2026, 04:002,016,382-1,518
3 Sept 2026, 22:592,017,900-982
2 Sept 2026, 10:432,018,882-230
1 Sept 2026, 10:472,019,112+21,279
31 Aug 2026, 11:281,997,833+44,447
30 Aug 2026, 10:571,953,386-886
29 Aug 2026, 07:351,954,272-1,399
28 Aug 2026, 04:131,955,671-1,721
27 Aug 2026, 07:251,957,392-1,029
26 Aug 2026, 08:251,958,421-743
25 Aug 2026, 05:181,959,164-1,990
24 Aug 2026, 06:131,961,154-1,527
22 Aug 2026, 12:461,962,681-1,345
20 Aug 2026, 23:381,964,026first reading

Engagement

344 posts held, back to 3 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 102 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
17.7%
avg views ÷ 2,061,968 subscribers
Avg views / post
365,000
220 posts measured
Reaction rate
0.338%
reactions ÷ views · ER floor
Posts in window
220
of 344 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 22 September 2026
Posts held344 (3 August 202622 September 2026)
Views total80,280,671
Reactions total271,073
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Sept 2026, 09:25 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
346
Videos
293
Links
706

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

Video runtime
8m 23s
Average length
16s

Measured directly from 31 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 212 of this channel’s own posts over the last 30 days: across 109 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 26 hours of being posted; a typical post has already reached 18.7% of its 24-hour view count within the first hour, and 57.1% within the first six; the median 24-hour reach across those posts is 163,000 views7.91% of this channel’s own subscriber count (90th percentile 996,400).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/182619 Sept 2026, 08:02 UTC184 minutes9.6 hours old103,000 views ~883 reactions60 minutes: 28,419 interp.3.0 hours: 54,699 interp.6.0 hours: 80,300still climbing at last readingnot yet at 24h2.7 hoursprovisional — final view count still climbing
/182518 Sept 2026, 19:31 UTC418 minutes22 hours old140,000 views ~812 reactions60 minutes: 24,051 interp.3.0 hours: 36,743 interp.6.0 hours: 44,30012 hours: 78,000still climbing at last readingnot yet at 24h11 hoursprovisional — final view count still climbing
/182418 Sept 2026, 18:39 UTC126 minutes26 minutes old18,800 views ~67 reactionsno checkpoint reading yetnot yet at 24hnot measurable yet
/182318 Sept 2026, 09:18 UTC5822 minutes32 hours old181,000 views ~820 reactions60 minutes: 29,081 interp.3.0 hours: 55,156 interp.6.0 hours: 80,00012 hours: 126,00024 hours: 155,000still climbing at last reading155,000measured7.6 hours
/182217 Sept 2026, 17:41 UTC24 minutes34 minutes old22,800 views ~52 reactionsno checkpoint reading yetnot yet at 24h15 minutesprovisional — final view count still climbing
/182117 Sept 2026, 17:04 UTC866 minutes2 days old214,000 views ~656 reactions60 minutes: 34,503 interp.3.0 hours: 61,0006.0 hours: 73,50012 hours: 93,50024 hours: 154,0002 days: 212,000still climbing at last reading154,000measured15 hours
/182017 Sept 2026, 16:30 UTC210 minutes41 minutes old26,900 views ~41 reactionsno checkpoint reading yetnot yet at 24h16 minutesprovisional — final view count still climbing
/181917 Sept 2026, 16:01 UTC859 minutes2 days old205,000 views ~196 reactions60 minutes: 36,007 interp.3.0 hours: 69,094 interp.6.0 hours: 85,60012 hours: 99,90024 hours: 149,0002 days: 201,000still climbing at last reading149,000measured13 hours

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

480,488 reactions across 344 posts, in 12 distinct kinds. The most used accounts for 60.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
290,27760.4%
🤪36,4087.58%
👾25,2895.26%
🔥21,5274.48%
👍20,7104.31%
🤗15,6583.26%
🎉12,9232.69%
🙏12,9002.68%
🆒12,7662.66%
👏11,9812.49%
🏆11,3752.37%
🤝8,6741.81%

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

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

Telegram Stars

Stars received
8,777
across the posts below
Posts paid on
259
of 344 we hold a reading for · 75%
Most on one post
771
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 344 most recent posts we hold for this entry, published 3 August 2026 to 22 September 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.291%
1 of 344 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
357,000
over 343 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 344 most recent posts we hold, published 3 August 2026 to 22 September 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

22 Sept 2026, 09:05 UTC≈12,500 views7 reactionsread 22 September 2026

✔️Включай наш VPN с обходом белых списков за пару кликов🔥

5👏1🤪1

22 Sept 2026, 08:37 UTC≈25,100 views29 reactionsread 22 September 2026
Photo

VPN С ОБХОДОМ БЕЛЫХ СПИСКОВ И ГЛУШИЛОК 🛜 В твоем регионе глушат мобильную сеть и всё перестало работать? Вот гайд на обход: 1️⃣ Переходим в бота: @AtlantaVPN_bot 2️⃣ Получаем БЕСПЛАТНЫЙ ключ за подписку на тгк 3️⃣ Подключаем ключ в Happ / INCY 5️⃣ Тестируем сервера Ловит даже в стратосфере. 👋 Подключить бесплатно сейчас: @AtlantaVPN

🔥1411👍3👏1

22 Sept 2026, 08:01 UTC≈37,100 views339 reactions2 Starsread 22 September 2026
Video

Это его первая охота, так что сделайте вид, что напугались, пожалуйста🥺 📲 Наш МАХ

247🤪37🤗23👍13👏5🏆4👾4🔥3

21 Sept 2026, 20:49 UTC≈97,900 views692 reactions3 Starsread 22 September 2026
Photo

Стесняшка 📲 Наш MAX

546🤗51🙏44🤪18👍7👾6🔥6🆒6

21 Sept 2026, 08:02 UTC≈166,000 views717 reactions9 Starsread 22 September 2026
Photo

Бобик 📲 Наш МАХ

536👍75🔥37👾23🤪17🤗15🎉5🙏5

20 Sept 2026, 20:06 UTC≈186,000 views882 reactions4 Starsread 22 September 2026
Photo

Спокойной ночи💋 📲 Наш МАХ

694🔥78🙏36🤪23🤗18👍11👾9🏆6

20 Sept 2026, 10:08 UTC≈219,000 views982 reactions1 Starread 22 September 2026
Video

Ну очень вкусная креветочка🤤 📲 Наш МАХ

733🔥74🤗71🤪28👾26👍14🙏11🆒10

19 Sept 2026, 19:03 UTC≈236,000 views1,182 reactions12 Starsread 22 September 2026
Photo

Лапками ать 📲 Наш MAX

959🤪65🙏48🤗46👍15🔥12🎉9👾9

19 Sept 2026, 08:02 UTC≈255,000 views1,259 reactions10 Starsread 22 September 2026
Photo

Обижулька 📲 Наш MAX

983🔥75👍70🤗35🎉26🤪20👾13🆒12

18 Sept 2026, 19:31 UTC≈268,000 views1,016 reactions18 Starsread 22 September 2026
Photo

Спокойной ночи 📲 Наш MAX

787🔥66🙏57🤗33👍15👾15🤪14🎉9

18 Sept 2026, 18:39 UTC≈18,800 views67 reactions1 Starread 18 September 2026

До итогов меньше суток, все успели поучаствовать?

51🤪8👾5🏆1👍1🆒1

18 Sept 2026, 09:18 UTC≈298,000 views976 reactions9 Starsread 22 September 2026
Video

Рабкотаем изо всех сил😪 📲 Наш MAX

758🤗84🤝42🤪32🔥14🙏12👍8👾8

Showing the 12 most recent of 344 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 2 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
8 September 2026

Forward network

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.

Mentions

Named by 6 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 19 September 2026 — this entry's latest reading, not the date you are reading this.

“Central TikTok ⚡️” (@CentralTikTok), 2,061,968 subscribers as measured 19 September 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.