Telegram RegisterThe public register of Telegram
Telegram profile photo for 바이킹 리서치

Channel

바이킹 리서치

@vikingstock

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

1,757subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001790772913
TypeChannel
Username@vikingstock
Description개인적으로 주식공부하는 자료들 모아두는 채널입니다. 뉴스와 애널리스트 리포트, 제 투자의견을 정리해서 올려 드리고 있습니다. 해당 채널의 게시물은 단순 의견 및 기록용도이고 매수-매도 등 투자권유를 의미하지 않습니다. 해당 게시물의 내용은 부정확할 수 있으며 매매에 따른 손실은 거래 당사자의 책임입니다. 해당 게시물의 내용은 어떤 경우에도 법적 근거로 사용될 수 없습니다
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded24 September 2026
Last confirmed live24 September 2026
Measurements held12
On Telegramt.me/vikingstock

Topic

Crypto & trading — 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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

1,7531,7621,757.57 August 2026 — 1,761 subscribers12 August 2026 — 1,760 subscribers15 August 2026 — 1,762 subscribers18 August 2026 — 1,760 subscribers22 August 2026 — 1,761 subscribers25 August 2026 — 1,759 subscribers28 August 2026 — 1,753 subscribers31 August 2026 — 1,755 subscribers4 September 2026 — 1,756 subscribers9 September 2026 — 1,758 subscribers13 September 2026 — 1,757 subscribers24 September 2026 — 1,757 subscribers1,7577 August 202624 September 2026
12 measurements spanning 47 days, net -4. 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,752–1,763 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Sept 2026, 01:311,757no change
13 Sept 2026, 01:361,757-1
9 Sept 2026, 12:181,758+2
4 Sept 2026, 14:181,756+1
31 Aug 2026, 21:131,755+2
28 Aug 2026, 15:341,753-6
25 Aug 2026, 08:361,759-2
22 Aug 2026, 03:471,761+1
18 Aug 2026, 14:441,760-2
15 Aug 2026, 18:451,762+2
12 Aug 2026, 01:121,760-1
7 Aug 2026, 18:251,761first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

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

“바이킹 리서치” (@vikingstock), 1,757 subscribers as measured 24 September 2026. Telegram Register, tgregister.com/channel/vikingstock.

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.