Telegram RegisterThe public register of Telegram

Channel

Invetas Signals

@invetas

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

198subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001227902311
TypeChannel
Username@invetas
DescriptionPublic technical analysis channel. Join our Discord! - https://discord.gg/chartkitchen https://chartkitchen.com
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/invetas

Topic

Crypto & trading — 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 100% 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@ChartKitchen/113226 Jul 2022, 17:39 UTC@invetas/3042 · this entry26 Jul 2022, 17:39 UTC1.00under a minute
@invetas/3044 · this entry28 Jul 2022, 11:54 UTC@ChartKitchen/113428 Jul 2022, 11:54 UTC1.00under a minute
@ChartKitchen/114118 Aug 2022, 10:00 UTC@invetas/3048 · this entry18 Aug 2022, 10:00 UTC1.00under a minute
@ChartKitchen/114323 Aug 2022, 19:17 UTC@invetas/3050 · this entry23 Aug 2022, 19:17 UTC1.00under a minute
@ChartKitchen/11449 Sept 2022, 08:22 UTC@invetas/3051 · this entry9 Sept 2022, 08:22 UTC1.00under a minute
@ChartKitchen/11459 Sept 2022, 08:31 UTC@invetas/3052 · this entry9 Sept 2022, 08:31 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@ChartKitchen16 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (115)

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 20 comparable posts for this entry, running 20 July 2022 to 24 January 2023. 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 @ChartKitchen. That is a statement about our reading window, not a claim of authorship.

Recorded under the key 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.

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

1986 Aug 2026, 06:00 — 198 subscribers7 Aug 2026, 04:32 — 198 subscribers6 Aug 2026, 06:007 Aug 2026, 04:32
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 197–199 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 04:32198no change
6 Aug 2026, 06:00198first reading

Engagement

20 posts held, back to 20 July 2022the 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 24 January 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
225
Links
2,100

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

Recent posts

24 Jan 2023, 09:04 UTC898 viewsread 7 August 2026

👑#BTC update: First daily close above the trendline in a year. Send it all up. Whole market. https://s3.tradingview.com/snapshots/i/IzBJfAsw.png

18 Jan 2023, 18:20 UTC393 viewsread 7 August 2026

👑#BTC update: SP500 resistance is acting as resistance should. Market pump posponed until the trendline breaks. https://s3.tradingview.com/snapshots/k/KL8udolI.png

15 Jan 2023, 08:49 UTC305 viewsread 7 August 2026

👑#BTC update: SP500 once again at its year long trendline resistance. If you're wondering why I'm posting about stocks, the market's still strongly correlated - BTC pump started as soon as SP500 made a higher low. At resistance now. Be careful with your overleveraged longs here fellas. Should be a volatile day tomorrow. Either a breakout or rejection. https://s3.tradingview.com/snapshots/3/3FMlTAyp.png

13 Dec 2022, 13:34 UTC304 viewsread 7 August 2026

👑#BTC update: 7.1% CPI announced (expected 7.3%). 50 basis points pretty much confirmed. Looks like the SPY trendline's getting broken. https://s3.tradingview.com/snapshots/6/6jNqiwaf.png

11 Dec 2022, 13:50 UTC232 viewsread 7 August 2026

👑#BTC update: Well, the weekly cloud's bottom once again held as support for SP500, while the FTX collapse pushed crypto lower. Stocks touched resistance last week - very precise chart. The next FOMC meeting is on Dec 13-14. The bond market is currently pricing in a 78.2% chance of a 50 bps rate hike. After 4 consecutive 75 bps rate hikes, 50 bps now would be the first tangible sign that the Fed is actually slowing

19 Oct 2022, 13:21 UTC260 viewsread 7 August 2026

👑#BTC update: Sorry for the lack of updates - BTC has just been consolidating for a couple of months now. SP500 has completed the weekly cloud's edge to edge trade. Touched the bottom edge and bounced. Disregarding the 2020 March black swan event, the cloud's bottom has been holding as support for over 13 years now. The last time a bottom edge bounce happened was during 2018 December - pretty much the exact bottom

9 Sept 2022, 08:31 UTC236 viewsread 7 August 2026

ATOM update: And it's hit. And even overshot it. Could have kept at 16. 53% up from entry right now. Public call. Now: https://s3.tradingview.com/snapshots/7/7cSvb69o.png Entry: https://s3.tradingview.com/snapshots/c/cgYh7vhp.png Call link: https://discord.com/channels/690955085127221308/691823346010292245/1002182065028083783

9 Sept 2022, 08:22 UTC206 viewsread 7 August 2026

ATOM update: Moved TP1 from $16 to $15.30. Just taking profits at cloud's top, which is currently at 15.30. Now: https://s3.tradingview.com/snapshots/n/njJoIW3W.png Entry: https://s3.tradingview.com/snapshots/c/cgYh7vhp.png Call link: https://discord.com/channels/690955085127221308/691823346010292245/1002182065028083783

23 Aug 2022, 19:17 UTC201 viewsread 7 August 2026

UNI, ETC, WOO, SNX stopped out on the latest crash few days ago. ETC one was annoying - at this point looks like a stop run, another cloud's top retest, liquidity tapped. Rebought because the merge is still happening, the narrative remains the same. Will sell if the daily actually closes below SL. https://s3.tradingview.com/snapshots/8/8Wxv7JzO.png

18 Aug 2022, 10:10 UTC227 viewsread 7 August 2026

UNI/USDT Kumo breakout, cloud's top touch. Bounce here will be the confirmation of trend reversal. Not a single alt call got stopped, and right now pretty much everything is at support - great R/R opportunities on most alts. If you felt like you missed out on something and didn't want to chase the pump couple of weeks ago, now's the time to get in.Entry: 8.11 SL: 7.49 TP1: 11.95 TP2: 13.79 https://s3.tradingview.co

18 Aug 2022, 10:00 UTC175 viewsread 7 August 2026

👑#BTC update: Continuous higher highs and higher lows - slowly grinding up for 2 months now. In the daily cloud, with the upper edge at 30299 USD. Right on the cloud's bottom edge at the moment, while most alts are on support. Logical place for a bounce. Probably another higher low is getting formed here. https://s3.tradingview.com/snapshots/9/9PQFLqkI.png

10 Aug 2022, 17:16 UTC185 viewsread 7 August 2026

COMP update: 💰🔥 TP1 hit! 🔥💰 First TP hit, 16% up, call from 12 days ago. Slowly grinding up. Middle of the cloud - temporary resistance, still expecting to complete the e2e to 100. Feel free to rebuy. Public call. Now: https://s3.tradingview.com/snapshots/f/FpgU6Mwc.png Entry: https://s3.tradingview.com/snapshots/f/FcTAPJUz.png Call link: https://discord.com/channels/690955085127221308/691823346010292245/1002970981

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

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

“Invetas Signals” (@invetas), 198 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/invetas.

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.