Вышла версия 1.0.6 🥽 Наконец-то я допилил Pico 4 версию! Главная новость для владельцев Pico 4 Ultra: в уровнях теперь 75–85 FPS, раньше было 13–15. На Quest 3 тоже стало немного легче, но пока не тестил. Я буквально выкладываю вам это из самолета! Как обновиться. Если сборщик у вас уже есть, он сам предложит обновление. Если нет, скачайте RepoQuestBuilder-1.0.6-win-x64.zip со страницы релиза, распакуйте и следуй…

Channel
KuVRa, ja pierdole 🇵🇱
@kuVRa_ru
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
60subscribers
+36 since we began measuring on 19 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004445332179 |
|---|---|
| Type | Channel |
| Username | @kuVRa_ru |
| Created | 16 October 2026 — measured — dated from the channel’s first post |
| First recorded | 19 October 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/kuVRa_ru |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 03:15 | 60 | +23 |
| 26 Oct 2026, 08:38 | 37 | +10 |
| 19 Oct 2026, 21:55 | 27 | +3 |
| 19 Oct 2026, 04:22 | 24 | no change |
| 19 Oct 2026, 03:47 | 24 | first reading |
Engagement
15 posts held, back to 16 October 2026 — the 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.
- ERR · 30 days
- 641.3%
- avg views ÷ 60 subscribers
- Avg views / post
- 385
- 13 posts measured
- Reaction rate
- 0.447%
- reactions ÷ views · ER floor
- Posts in window
- 15
- of 15 held
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 11 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 18 October 2026 |
|---|---|
| Posts held | 15 (16 October 2026 – 18 October 2026) |
| Views total | 5,002 |
| Reactions total | 22 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 19 Oct 2026, 04:22 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.
What this channel posts
- Video runtime
- 3m 21s
- Average length
- 1m 41s
Measured directly from 2 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
22 reactions across 11 posts, in 5 distinct kinds. The most used accounts for 36.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 8 | 36.4% | |
| ❤ | 7 | 31.8% | |
| 👍 | 4 | 18.2% | |
| 🥰 | 2 | 9.09% | |
| 👌 | 1 | 4.55% |
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 15 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 22 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 16 October 2026 to 18 October 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.
Recent posts
Pico 4 Ultra: вылечили! 🎉 Пациент скорее жив. В итоге мы (я и Плотва) выяснили что драйвер Ultra очень долго копирует картинку. Копировалась сразу вся картинка для обоих глаз. Ultra на это тратит около 50мс, что просто вечность для виара. В итоге это оказался эффект, который затемняет края экрана, когда на тебя смотрит монстр. (Особенно глаз на потолке) Этот баг работал всегда, даже когда его не было видно. Теперь…
❤3
Pico 4 Ultra REPO: часть третья 🩺 Отладка через телегу ощущается так, как будто мы делаем операцию по почте. Собираем билд, тестим, берем логи, и так по кругу. Результаты большого теста: Ни одно отключение не помогло. Без теней, частиц, видео, освещения и постобработки в игре видны всё те же 12–13 FPS. Даже если выключить всё это, получается только 19 FPS. Пока совсем непонятно почему же шлем, который мощнее, не тя…
❤1
Lethal Company в Quest 3 Три дня назад начал переносить Lethal Company вместе с VR-модом LCVR на Quest 3, и уже задолбался)) 🚀 Что уже работает • Игра запускается на шлеме в VR: главное меню, корабль, посадка на планету, руки и взаимодействия из LCVR. • Можно хостить игру по LAN, соединение со шлема до ПК проверено. • Графика. Оригинал сделан на HDRP, а его на Android нет. Пришлось перевести всё на URP и подгонять …
🔥2
Pico 4 Ultra: продолжение пирожкового детектива 🔍 Нора оказалась глубже. Сначала я подумал что в одном из замеров система держала игру на «фоновых» ядрах, среди которых два медленных. Мне даже показалось, что он две игры сразу запустил. Но в итоге это бы не так. Типичный red herring. После нескольких итераций мы узнали что в игре по-прежнему 13 FPS, а процессор при этом простаивает. Видеочип тоже ничем не нагружен…
❤2
Появился автономный VR-мод R.E.P.O. для Quest 3 Наш подписчик собрал мод, который позволит вам поиграть в кооперативный френд-слоп хоррор R.E.P.O. на Quest 3. Поддерживается кроссплей с пользователями из Steam. Доступно по ссылке. Мод уважает права разработчиков и использует лицензионные файлы из официальной сборки. Для установки понадобятся небольшие манипуляции, но все инструкции есть на GitHub.
🔥2
Еее, попал в подборку новостей https://www.youtube.com/watch?v=XZ1tLkt_T0Y
🔥2
Кстати, для REPO у меня есть ещё маленький мод который просто добавляет зеркало в трак. Чтобы вы могли сфоткаться со всеми своими косметиками)) https://thunderstore.io/c/repo/p/Dobutsu/TruckMirror/
👍1
Как дела с Pico 4 Ultra 🥽 Так получилось что я теперь делаю ещё и версию REPO для Pico. У меня самого Pico нет, поэтому всё проверяет подписчик. Процесс медленный, но дело двигается потихоньку. Что получилось: Игру удалось запустить на Pico. Изначально порт сделан под Quest, и для Pico его приходится дополнительно переделывать через ovrport. Игра больше не вылетает при первом запуске(лол), когда шлем спрашивает р…
👍1
Проверка комментов
Work in Progress...
🔥2❤1
Сейчас работаю над портом Lethal Company. Пока что идёт тяжело, так как игра держит все свои файлы в памяти одновременно, а не подгружает по мере необходимости. Пока что идёт в 30fps, что для шлема, мягко сказать, маловато. Сегодня попробую записать видео.
👍2🥰2
Showing the 12 most recent of 15 posts we hold for @kuVRa_ru. 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.
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
Named by 2 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.
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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“KuVRa, ja pierdole 🇵🇱” (@kuVRa_ru), 60 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/kuVRa_ru.
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.