Telegram RegisterThe public register of Telegram
Telegram profile photo for jugoloss

Channel

jugoloss

@jugoloss

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

41subscribers

-1 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-1002285811022
TypeChannel
Username@jugoloss
CreatedBetween 1 September 2024 and 4 January 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/jugoloss

Growth

414241.57 August 2026 — 42 subscribers10 August 2026 — 42 subscribers15 August 2026 — 41 subscribers7 August 202615 August 2026
3 measurements spanning 8 days, net -1. 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 41–42 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 19:0641-1
10 Aug 2026, 17:1742no change
7 Aug 2026, 14:0442first reading

Engagement

18 posts held, back to 4 January 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 18 posts for this entry, the most recent from 3 September 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3m 21s
Average length
40s

Measured directly from 5 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

25 reactions across 11 posts, in 5 distinct kinds. The most used accounts for 60.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1560.0%
👍624.0%
🗿28.00%
👀14.00%
🤯14.00%

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

Measured over the 18 most recent posts we hold, published 4 January 2025 to 3 September 2025, 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

3 Sept 2025, 16:12 UTC≈1,230 views4 reactionsread 10 August 2026
Photo

🚨 6figs друг обнулился на щитках С самого старта меты щитков на Солане я был против. Зашёл → потерял пару тысяч → больше туда не возвращался. Для меня это всегда было и остаётся 🎰 чистым казиком: стреляют единицы, а 99.9% проектов — раг с самого начала. ⚙️ Немного про механику: • софты гоняют актив, создавая «органику» через сотни несвязанных кошельков; • параллельно команда ведёт Twitter, TG, стримы — создаёт илл

4

19 Jun 2025, 18:23 UTC≈1,320 views2 reactionsread 10 August 2026
Forwarded from @OfficialBAYCVideo

The first official BAYC sticker pack drops tomorrow. 🗓 Get ready! 🌟

2

13 Jun 2025, 14:04 UTC857 viewsread 10 August 2026

https://stickerdom.store/bundle/1/24 по идее правильный линк (если брать за тон)

13 Jun 2025, 11:59 UTC786 views1 reactionsread 10 August 2026

Bringing Azuki to Telegram in the Year of the Snake. It's time for transformation, growth, and connection. ⛩

1

26 Feb 2025, 21:55 UTC≈1,010 views1 reactionsread 10 August 2026

🔥 Страх и неопределенность на рынке 🔥 По всем телеграм-каналам — нереальный страх. Индекс страха и жадности на 20% (сильный страх). Солана застыла (130-140), а биток просел. Для меня это хорошая новость — "трамп памп" перелили в биточек, поэтому он стоял на месте всё это время (одна из причин). Слабые руки вышли, и теперь солана перестала лететь вниз. Когда биточек падает — если это не знак, то что? Когда рынок в

👀1

29 Jan 2025, 14:17 UTC714 viewsread 10 August 2026
Video

Closing party 26 January. После Берна кота увидел такую картину в общем зале и ушел домой .

29 Jan 2025, 14:09 UTC709 viewsread 10 August 2026
Video

На протяжении 2 дней за мяу все вот так бегали .

27 Jan 2025, 15:45 UTC611 views1 reactionsread 10 August 2026

Только сейчас я понял, насколько важно ходить на такие мероприятия. Почему это необходимо? 🔹 Вы среди своих Это ваша среда, где все занимаются тем же, чем и вы. Здесь легко чувствовать себя комфортно. 🔹 Новые знания и идеи На таких ивентах всегда можно узнать много инсайтов, обсудить тренды и задать вопросы, которые давно вас интересовали. 🔹 Нетворкинг решает всё Я познакомился с десятками людей, половина из кото

🤯1

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

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.

Mentions

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.

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

“jugoloss” (@jugoloss), 41 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/jugoloss.

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.