How many hours/week do you actually work? ⏰
- ⏰ Under 20 (part-time)13%
- 💼 20-30 (balanced)0%
- 🔥 30-40 (full grind)50%
- 😤 40+ (send help)38%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
❤1

Channel
@ChronotechNEWS
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Telegram's recommendations · Domains linked from posts · Cite this entry
1,028,617subscribers
-51,004 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001417455250 |
|---|---|
| Type | Channel |
| Username | @ChronotechNEWS |
| Description | Chrono.tech — Blockchain products for HR. earn crypto freelancing: laborX.com Linktree: https://linktr.ee/chrono.tech |
| Created | 24 February 2019 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/ChronotechNEWS |
Technology — 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 73% 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.
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.
Posts published here appear word for word on 2 other registered channels. They sit inside a group of 9 channels that share the same post bodies with each other. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @ChronotechNEWS/332 · this entry14 Jan 2023, 13:37 UTC | @NewsPlayToEarn/5614 Jan 2023, 13:37 UTC | 1.00 | under a minute |
| @ChronotechNEWS/342 · this entry19 Jan 2023, 11:23 UTC | @NewsPlayToEarn/6519 Jan 2023, 11:23 UTC | 1.00 | under a minute |
| @NewsPlayToEarn/7124 Jan 2023, 13:31 UTC | @ChronotechNEWS/348 · this entry24 Jan 2023, 13:31 UTC | 1.00 | under a minute |
| @ChronotechNEWS/389 · this entry18 Feb 2023, 17:06 UTC | @NewsPlayToEarn/11018 Feb 2023, 17:06 UTC | 1.00 | under a minute |
| @NewsPlayToEarn/15731 Mar 2023, 17:50 UTC | @ChronotechNEWS/436 · this entry31 Mar 2023, 17:50 UTC | 1.00 | under a minute |
| @NewsPlayToEarn/18618 Apr 2023, 15:51 UTC | @ChronotechNEWS/465 · this entry18 Apr 2023, 15:51 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @NewsPlayToEarn | 91 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (64–27) |
| @TimeFarmChannel | 10 (8/8 hand-verifiable sample passed) | 1.00 | 2 minutes | even |
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 32 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 1,442 comparable posts for this entry, running 24 February 2019 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.
Across the whole group of 9, the earliest publisher we hold is @ChronotechNEWS — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_mutual · clone_source, last confirmed 7 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.
This channel’s posts match, word for word or near enough, posts on 8 other registered channels, 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 12:39 | 1,028,617 | -4,819 |
| 4 Sept 2026, 14:58 | 1,033,436 | -2,731 |
| 3 Sept 2026, 00:37 | 1,036,167 | -1,679 |
| 1 Sept 2026, 21:05 | 1,037,846 | -1,921 |
| 31 Aug 2026, 23:47 | 1,039,767 | -1,602 |
| 30 Aug 2026, 22:27 | 1,041,369 | -1,750 |
| 30 Aug 2026, 00:07 | 1,043,119 | -1,245 |
| 28 Aug 2026, 22:16 | 1,044,364 | -1,818 |
| 27 Aug 2026, 21:12 | 1,046,182 | -1,050 |
| 26 Aug 2026, 22:25 | 1,047,232 | -1,425 |
| 25 Aug 2026, 23:12 | 1,048,657 | -1,514 |
| 25 Aug 2026, 02:04 | 1,050,171 | -2,217 |
| 23 Aug 2026, 14:34 | 1,052,388 | -2,903 |
| 22 Aug 2026, 01:08 | 1,055,291 | -1,951 |
| 20 Aug 2026, 19:15 | 1,057,242 | -1,257 |
| 19 Aug 2026, 18:22 | 1,058,499 | -1,391 |
| 18 Aug 2026, 18:35 | 1,059,890 | -1,561 |
| 17 Aug 2026, 16:55 | 1,061,451 | -1,793 |
| 16 Aug 2026, 14:34 | 1,063,244 | -2,882 |
| 14 Aug 2026, 22:24 | 1,066,126 | first reading |
1,978 posts held, back to 24 February 2019 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 181 pages 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 110 of 133 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 September 2026 |
|---|---|
| Posts held | 1,978 (24 February 2019 – 9 September 2026) |
| Views total | 52,642 |
| Reactions total | 176 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Sept 2026, 02:35 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 10 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
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 91 of this channel’s own posts over the last 30 days: across 80 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 12 hours of being posted; a typical post has already reached 25.7% of its 24-hour view count within the first hour, and 53.7% within the first six; the median 24-hour reach across those posts is 278 views — 0.027% of this channel’s own subscriber count (90th percentile 311).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /201328 Aug 2026, 20:05 UTC | 130 minutes – 30 minutes old | 55 viewsno reaction reading | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /201228 Aug 2026, 20:01 UTC | 133 minutes – 33 minutes old | 68 views1 reaction | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /201128 Aug 2026, 18:12 UTC | 279 minutes – 2.4 hours old | 126 views1 reaction | no checkpoint reading yetstill climbing at last reading | not yet at 24h | 79 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /200827 Aug 2026, 19:33 UTC | 238 minutes – 1.5 hours old | 77 views1 reaction | 60 minutes: 63 interp. | not yet at 24h | 38 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /200727 Aug 2026, 19:31 UTC | 240 minutes – 1.6 hours old | 78 views1 reaction | 60 minutes: 64 interp. | not yet at 24h | 40 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
| /200426 Aug 2026, 19:48 UTC | 318 minutes – 1.6 hours old | 76 views2 reactions | 60 minutes: 59still climbing at last reading | not yet at 24h | 30 minutesprovisional — final view count still climbing |
| /200326 Aug 2026, 16:39 UTC | 87 minutes – 4.8 hours old | 172 viewsno reaction reading | 60 minutes: 75 interp. → 3.0 hours: 117still climbing at last reading | not yet at 24h | 75 minutesprovisional — final view count still climbing |
| /200226 Aug 2026, 16:34 UTC | 811 minutes – 4.9 hours old | 182 views2 reactions | 60 minutes: 90 interp. → 3.0 hours: 133still climbing at last reading | not yet at 24h | 61 minutesprovisional — 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.
223 reactions across 141 posts, in 13 distinct kinds. The most used accounts for 20.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 45 | 20.2% | |
| 🔥 | 41 | 18.4% | |
| 👍 | 40 | 17.9% | |
| 🤯 | 34 | 15.2% | |
| 👀 | 29 | 13.0% | |
| ⚡ | 24 | 10.8% | |
| 🤩 | 3 | 1.35% | |
| 🙈 | 2 | 0.897% | |
| ❤🔥 | 1 | 0.448% | |
| 😁 | 1 | 0.448% | |
| 😍 | 1 | 0.448% | |
| 🤓 | 1 | 0.448% | |
| 🤣 | 1 | 0.448% |
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 706 of the 1,000 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 3,496 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 2 January 2025 to 9 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.
How many hours/week do you actually work? ⏰
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
❤1
🔥 Hot Gig: Crypto Marketing Specialist 🛠 Skills: Growth Hacking 💰 Range: $3,000-8,000 📋 Launch and promote Web3 products Web3 talent is in demand. If you've got the skills, the gigs are waiting. Interested? Check out similar gigs on LaborX 👇 #ChronoTech #LaborX #Web3Jobs #Freelancing #Crypto #FutureOfWork Learn | News | 𝕏 takes
❤1👀1
🤖 What AI is doing today You're Filing AI Income But the IRS Has No Rules Yet #Shorts Tax agencies punted AI income to 2026—but people are filing now. Nobody knows how to tax it yet. ▶️ Watch (30s): https://youtube.com/shorts/RsrM5s20JRw #ai #aijobs #futureofwork #shorts Learn | News | 𝕏 takes
👍2
How do you find new clients?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
🔥 Hot Gig: Rust Developer 🛠 Skills: Solana/Substrate 💰 Range: $5,000-18,000 📋 Build on Solana or Polkadot Web3 talent is in demand. If you've got the skills, the gigs are waiting. Interested? Check out similar gigs on LaborX 👇 #ChronoTech #LaborX #Web3Jobs #Freelancing #Crypto #FutureOfWork Learn | News | 𝕏 takes
❤2🤯1
📊 Did you know? The average freelancer on LaborX earns across 3 different blockchain ecosystems. The future of work is decentralized. Are you ready? #ChronoTech #LaborX #Web3Jobs #Freelancing #Crypto #FutureOfWork Learn | News | 𝕏 takes
❤🔥1👍1
🔥 Hot Gig: Web3 Community Manager 🛠 Skills: Discord/Telegram 💰 Range: $2,000-6,000 📋 Grow and engage crypto communities Web3 talent is in demand. If you've got the skills, the gigs are waiting. Interested? Check out similar gigs on LaborX 👇 #ChronoTech #LaborX #Web3Jobs #Freelancing #Crypto #FutureOfWork Learn | News | 𝕏 takes
🤯1🙈1
📊 Did you know? 72% of Gen Z professionals prefer freelancing over traditional employment. The future of work is decentralized. Are you ready? #ChronoTech #LaborX #Web3Jobs #Freelancing #Crypto #FutureOfWork Learn | News | 𝕏 takes
👍1🤯1
🔥 Hot Gig: Smart Contract Developer 🛠 Skills: Solidity 💰 Range: $5,000-15,000 📋 Build and audit DeFi protocols Web3 talent is in demand. If you've got the skills, the gigs are waiting. Interested? Check out similar gigs on LaborX 👇 #ChronoTech #LaborX #Web3Jobs #Freelancing #Crypto #FutureOfWork Learn | News | 𝕏 takes
🔥1🤣1
Portfolio or resume — what wins more gigs? 📄
Shares as published. No per-option vote count is published by Telegram, so none is shown.
💡 Freelancer Tip: From freelancer to agency Many top LaborX freelancers have scaled into agencies: 1. Start solo, build a reputation 2. Find complementary freelancers (designer + dev) 3. Take on larger projects together 4. Create a team profile 5. Earn more by managing, not just doing The future of work is decentralized teams. Save this for later 📌 #ChronoTech #LaborX #Web3Jobs #Freelancing #Crypto #FutureOfWork…
❤2🔥1
🌐 DBS and Citi complete weekend USD payment via Swift’s Digital Ledger using tokenized deposits This matters for the Web3 workforce. Here's why you should pay attention. 🔗 Read more — CoinDesk am I tripping? Learn | News | 𝕏 takes
⚡1
Showing the 12 most recent of 1,978 posts we hold for @ChronotechNEWS. 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 6 most recent of 42 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.
How many hours/week do you actually work? ⏰
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
How do you find new clients?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Portfolio or resume — what wins more gigs? 📄
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Will DAOs replace traditional companies?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
How many clients do you juggle at once? 🤹
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Your biggest freelancing win?
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 1,000 most recent posts we hold (the sample is capped at 1,000), published 2 January 2025 to 9 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@ChronotechNEWS named 71 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
21 more handles are in this same list but not shown individually here — capped at 50.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 8 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 16 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
10 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.
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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“Chrono.tech NEWS” (@ChronotechNEWS), 1,028,617 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/ChronotechNEWS.
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.