Telegram RegisterThe public register of Telegram

Channel

Timecoin_UNofficial

@Timecoin_Official

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry

884subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001976125715
TypeChannel
Username@Timecoin_Official
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/Timecoin_Official

Topic

Other / unclassifiable — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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 (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@Timecoin_Official/74 · this entry28 Oct 2025, 17:42 UTC@Time_Lovers_Community/23328 Oct 2025, 17:42 UTC1.00under a minute
@Timecoin_Official/79 · this entry19 Nov 2025, 08:44 UTC@Time_Lovers_Community/23719 Nov 2025, 08:44 UTC1.00under a minute
@Timecoin_Official/99 · this entry17 Dec 2025, 22:35 UTC@Time_Lovers_Community/25517 Dec 2025, 22:35 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@Time_Lovers_Community5 (5/5 hand-verifiable sample passed)1.00under a minute@Time_Lovers_Community (41)

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 3 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 7 comparable posts for this entry, running 4 June 2025 to 17 December 2025. 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 @Timecoin_Official — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 8 August 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

8847 Aug 2026, 15:32 — 884 subscribers8 Aug 2026, 01:05 — 884 subscribers7 Aug 2026, 15:328 Aug 2026, 01:05
2 measurements taken within a single day. 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 883–885 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 01:05884no change
7 Aug 2026, 15:32884first reading

Engagement

20 posts held, back to 4 May 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 25 January 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
19
Videos
5
Links
10

Lifetime counters from Telegram’s own channel header, read 8 August 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
47s
Average length
24s

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

Reaction mix

140 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 32.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4632.9%
3424.3%
👎2316.4%
🔥1812.9%
🤝96.43%
🎉53.57%
🫡32.14%
😁21.43%

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

Measured over the 20 most recent posts we hold, published 4 May 2025 to 25 January 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.

Recent posts

25 Jan 2026, 14:10 UTC≈2,890 views3 reactionsread 8 August 2026

Warning to new users, don't take risks. ⚠️ read this

🤝3

1 Jan 2026, 18:09 UTC≈2,940 views3 reactionsread 8 August 2026
Photo

Just sketched a logo for my sperm donorship program. Is ‘pd’ in a circle minimalist enough?

👍3

17 Dec 2025, 22:35 UTC≈2,410 views7 reactionsread 8 August 2026
Photo

do nothing 🌍 avg person spends 6+ hours a day online. that's roughly 40% of waking time most of it goes to feeds, short videos, messages, and more now people check their phones 50–150 times a day. often without noticing. waiting in line, sitting in transport, even walking – every pause gets filled this constant input makes “doing nothing” feel unfamiliar in a 2014 study by Wilson et al. (Science), people were le

👍7

3 Dec 2025, 14:51 UTC≈1,780 views2 reactionsread 8 August 2026

🐣 It happened. Our decentralized confidential compute network, Cocoon, is live. The first AI requests from users are now being processed by Cocoon with 100% confidentiality. GPU owners are already earning TON. https://cocoon.org is up, with docs and the source code. 🤔 Centralized compute providers such as Amazon and Microsoft act as expensive intermediaries that drive up prices and reduce privacy. Cocoon solves both

👍2

24 Nov 2025, 09:13 UTC≈1,580 views6 reactionsread 8 August 2026
Video

I couldn't find a suitable caption.

👍3🤝3

20 Nov 2025, 20:50 UTC≈1,560 views4 reactionsread 8 August 2026
Forwarded from @thenotgamesPhoto

🎙 Not Just Games · Episode 3 AI in Game Design: The End or the Start of a Golden Age? 🗓 November 21, 3PM UTC 🌐 https://x.com/i/spaces/1kvJpMjkXlmxE AI is moving into game design whether we like it or not. Some builders see the beginning of a new creative era. Others think something important is being lost along the way. This episode brings both sides to one table. 🎨 END OF AN ERA – FAB (Boinkers) – Camol (Suga

🔥2🎉1👍1

19 Nov 2025, 08:44 UTC≈1,040 views3 reactionsread 8 August 2026
Video

🌐 TON Foundation at Devconnect Argentina Join TON Foundation and leading Web3 organizations at Devconnect in Argentina. Connect with global builders and explore Web3 innovation. Partners: tApps Center, Houdini Swap, Tonco. 📍 November 19 | Startup Palacio 🔗 Register: https://luma.com/wxhk2tou

👍2🔥1

29 Oct 2025, 18:10 UTC≈1,800 views4 reactionsread 8 August 2026
Photo

https://x.com/ton_blockchain/status/1983566748235231668 @cocoon

🎉4

29 Oct 2025, 18:09 UTC≈1,890 views3 reactionsread 8 August 2026
Forwarded from @cocoon

Welcome to Cocoon — the Confidential Compute Open Network Cocoon is a decentralized network for executing AI inference securely and privately. In this network, app developers reward GPU owners with TON for processing inference requests. Telegram will be the first major customer to use Cocoon for confidential AI queries — and will invest heavily in promoting the network across its global ecosystem. 🔨 App developer

🔥3

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

3 Jun 2025, 18:13 UTCAnonymous Poll334 voters

They abandoned the [main channel+ official username] of the project, this is the only living community of this dead project... so, What should I do with this situation?

  1. Why didn't you scam us with a fake project?31%
  2. Delete this channel and username, completely destroy the community.20%
  3. Hold on, we're here and we're not taking any risks.28%
  4. I'll say it in the comments.13%
  5. check result44%

The shares total 136%, 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.

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 20 most recent posts we hold, published 4 May 2025 to 25 January 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.

Citation-graph rank

Citation-graph rank — 1,128,593 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

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

“Timecoin_UNofficial” (@Timecoin_Official), 884 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Timecoin_Official.

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.