Telegram RegisterThe public register of Telegram
Telegram profile photo for TRADING VIEW PREMIUM ACCOUNT SELLER

Channel

TRADING VIEW PREMIUM ACCOUNT SELLER

@cheap_tradingview_premium

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

400subscribers

+19 since we began measuring on 23 August 2026

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

Register entry

Telegram ID-1001570703526
TypeChannel
Username@cheap_tradingview_premium
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded23 August 2026
Last confirmed live17 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/cheap_tradingview_premium

Topic

Marketing & affiliate — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 48% 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.

Growth

381400390.523 August 2026 — 381 subscribers23 August 2026 — 381 subscribers30 August 2026 — 386 subscribers9 September 2026 — 390 subscribers17 September 2026 — 400 subscribers23 August 202617 September 2026
5 measurements spanning 25 days, net +19. 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 378–403 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 20:21400+10
9 Sept 2026, 04:16390+4
30 Aug 2026, 16:44386+5
23 Aug 2026, 10:00381no change
23 Aug 2026, 09:45381first reading

Engagement

20 posts held, back to 3 July 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 page of 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 May 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

25 May 2026, 17:54 UTC190 viewsread 23 August 2026
Photo

334 I'd sold for trading view premium subscription 🚀🚀🚀🚀

25 May 2026, 17:54 UTC188 viewsread 23 August 2026
Photo

333 I'd sold for trading view premium subscription 🚀🚀🚀🚀

25 May 2026, 17:53 UTC157 viewsread 23 August 2026
Photo

332 I'd sold for trading view premium subscription 🚀🚀🚀🚀

25 May 2026, 17:52 UTC146 viewsread 23 August 2026
Photo

331 I'd sold for trading view premium subscription 🚀🚀🚀🚀

23 May 2026, 12:36 UTC170 viewsread 23 August 2026

TRADINGVIEW.COM PREMIUM PLAN FEATURES ●8 charts per tab ●25 indicators per chart ●20K historical bars ●50 parallel chart connections ●400 price alerts ●400 technical alerts ●2 watchlist alerts ●Web, desktop and mobile apps ●No ads ●Volume profile ●Custom timeframes ●Custom Range Bars ●Multiple watchlists ●Bar Replay ●Indicators on indicators ●Chart data export ●Intraday Renko, Kagi, Line Break, Point & Figure chart

23 May 2026, 11:35 UTC158 viewsread 23 August 2026
Photo

330 I'd sold for trading view premium subscription 🚀🚀🚀🚀

29 Oct 2025, 10:58 UTC494 viewsread 23 August 2026
Photo

329 I'd sold for trading view pro plus subscription 🚀🚀🚀🚀

29 Oct 2025, 10:57 UTC450 viewsread 23 August 2026
Photo

328 I'd sold for trading view pro plus subscription 🚀🚀🚀🚀

16 Oct 2025, 08:46 UTC392 viewsread 23 August 2026
Photo

327 I'd sold for trading view premium subscription 🚀🚀🚀🚀

7 Oct 2025, 06:04 UTC367 viewsread 23 August 2026
Photo

326 I'd sold for trading view premium subscription 🚀🚀🚀🚀

7 Oct 2025, 06:03 UTC303 viewsread 23 August 2026
Photo

325 I'd sold for trading view premium subscription 🚀🚀🚀🚀

12 Sept 2025, 06:54 UTC297 viewsread 23 August 2026
Photo

324 I'd sold for trading view premium subscription 🚀🚀🚀🚀

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

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.

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

“TRADING VIEW PREMIUM ACCOUNT SELLER” (@cheap_tradingview_premium), 400 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/cheap_tradingview_premium.

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.