Channel
@run4j
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
78subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002474482735 |
|---|---|
| Type | Channel |
| Username | @run4j |
| Created | Between 1 September 2024 and 8 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/run4j |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 16:36 | 78 | +1 |
| 9 Aug 2026, 20:17 | 77 | no change |
| 7 Aug 2026, 18:23 | 77 | first reading |
20 posts held, back to 8 March 2025 — 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 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 2 June 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
115 reactions across 19 posts, in 4 distinct kinds. The most used accounts for 72.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 83 | 72.2% | |
| 🔥 | 22 | 19.1% | |
| 👏 | 7 | 6.09% | |
| ❤ | 3 | 2.61% |
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 19 of the 20 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 115reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 8 March 2025 to 2 June 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.
🚀 Tez kunda! Run4j to‘liq ochiq kodli bo‘ladi. Kod hamjamiyatniki. 🌐 Sayt: https://run4j.com 📖 Doc: https://docs.run4j.com ☁️ Cloud install: https://docs.run4j.com/en/install-cloud 🔗 Docker install: https://docs.run4j.com/en/install-docker 🔗 Docker Hub: https://hub.docker.com/r/run4j/run4j-community 📨 Telegram: @run4j 📨 Telegram guruh: @run4j_chat ❓ Savol va takliflar uchun: @java_maniac
🔥2👍1
Workflow Automation platformalarni shunchaki funksiyalariga qarab emas, balki qanday ustuvorlik (falsafa) asosida qurilganiga qarab farqlash to‘g‘riroq bo'ladi. Umuman olganda, jarayonlarni bajarishda asosan 3 xil yondashuv borligini ko‘rishimiz mumkin: 1. Tezlik birinchi o‘rinda (Performance First) Bu yondashuvda asosiy maqsad — tezlik. Ya'ni ma'lumotlar minimal kechikish bilan, real vaqt rejimida qayta ishlanadi.…
👍3🔥3👏1
“Java automation uchun mos emas.” Shunaqa gapni ko‘p eshitamiz. Automation desa: Python, Javascript va Bash Java esa: Og'ir, sekin ishga tushadi, faqat enterprise backend uchun - To‘g‘rimi? Yo‘q. Muammo Java’da emas. Muammo — uni qanday ishlatayotganimizda. Chunki: JAR build qilinadi, deploy qilinadi, restart qilinadi, konfiguratsiya qilinadi vahokazo. Bunaqa ishlatish Build-time modelga bog'langan static deploy…
👍5
Low-code toollarni yomon ko‘rasiz, lekin kod yozishni yaxshi ko‘rasizmi? Ko‘p automation platformalar tez boshlash imkonini beradi, lekin murakkabroq mantiq kerak bo‘lganda sizni cheklab qo‘yadi. Run4j — bu execution-first platforma: siz workflow’ni vizual tarzda ko‘rishingiz mumkin, lekin barcha muhim mantiq haqiqiy kod orqali yoziladi. Bu yerda “platforma ruxsat bermaydi” degan muammo yo‘q. Qaysi til qulay bo‘ls…
👍6
Vibecoder akani serveriga Coolify o‘rnatib, uni Run4j yordamida Telegram botga uladik. Qulay tarafi shundaki, endi serverni shunchaki ovozli xabarlar bilan boshqarish imkoniyati bor. Ovozni matnga aylantirish uchun Aisha AI xizmatidan foydalandik. Bu yechim boshqalarga ham asqotib qolar deb, Aisha AI bilan ishlash uchun kerakli skriptlarni Run4j marketplace’ga joylab qo‘ydik. Agar ovozli funksiyalari bor loyiha qil…
👍4🔥1
Run4j orqali Run4j'ni boshqarish)) Ko‘pchilik Run4j yordamida nimalar qilish mumkinligi haqida so‘rab turadi. Ichki jarayondan misol keltirmoqchi edim. Hozirda Run4j Cloud’dagi bepul versiyalarni o‘rnatish va boshqarish tizimi to‘liq Run4j’ning o‘zida yozilgan. Hammasi juda sodda ishlaydi: - Foydalanuvchi saytdan ro‘yxatdan o‘tib, so‘rov yuboradi. - Biz admin paneldan (bu ham Run4j da qilingan) ruxsat beramiz. - Q…
👍7
Telegram bot yaratishda qanaqadir kutubxonalarni ishlatmasdan sof Telegram Bot Api yordamida to'liq nazoratli bot yaratib ko'rganmisiz? Run4jda shunday qilish mumkin. API ni haqiqiy shakli bilan jarayonni to'liq kuzatish bilan birga juda oson bot yozish mumkin. 🔗 Docker Hub: https://hub.docker.com/r/run4j/run4j-community 🌐 Sayt: https://run4j.com 📖 Dokumentatsiya: https://docs.run4j.com ☁️ Cloud install: https://doc…
👍4
Run4j platformasi imkoniyatlarini namoyish qilish maqsadida maksimal overengineering qilingan😅, Suratsoz deb nomlangan bot loyihasini Marketga yukladik. Bu bot Nanobanana API yordamida ishlaydi va foydalanuvchi yuborgan rasmlarni oldindan tayyorlangan maxsus promptlar asosida o'zgartirish imkonini beradi. Loyiha ichida ko'pchilikni qiziqtiradigan manual to'lov tizimi ham amalga oshirilgan. Bunda foydalanuvchi karta …
👍7
Avtomatlashtirishda moslashuvchanlik muhimmi? Dunyoda n8n, Make, Node-red yoki Windmill kabi platformalar juda mashhur va ko‘p holatlarda ishni osonlashtiradi. Lekin biz Run4j ustida ishlayotganimizda bir narsani ustuvor qilib oldik: dasturchi uchun cheklovlarni kamaytirish va maksimal moslashuvchanlik (flexibility) berish. Ba'zida tayyor bloklar bilan ishlash qulay, lekin murakkabroq mantiq kerak bo'lganda to'liq …
👍6🔥1
Run4j platformasini Community versiyasini hamma uchun ochiq holatda Docker Hub’ga chiqardik. Run4j — bu skriptlarni avtomatlashtirish va turli jarayonlarni (workflow) bir-biriga oson bog‘lash uchun mo‘ljallangan oddiy vosita. Ishimizni biroz bo‘lsa-da yengillashtirish maqsadida quyidagi imkoniyatlarni qo‘shganmiz: 🔹 Tezkor bajarish: Skriptlarni real vaqtda yurgizish va loglarni kuzatish. 🔹 Vizual Builder: Jarayonlar…
👍5❤1👏1
Run4j yordamida API yaratish. Run4j APIlar yaratish uchun juda qulay. Full koddan No-codegacha to'liq API larni boshqarish mumkin. Videoda boshlang'ich qismlar ko'rsatilgan. Video ovozi ingliz tilida, lekin o'zbekcha subtitr mavjud. Keyingi video Run4jda databaselar bilan ishlash haqida bo'ladi. 🌐 Run4j 💬 @run4j https://youtu.be/BtbfW6clrwg?si=vmV9P8y0W6UR2OhS
👍3❤1
🎥 Biz Run4j Quick start videolarini yozishni boshladik. Birinchi video havolasi quyida ko'rsatilgan. Ovoz ingliz tilida, lekin subtitrda rus va o'zbek tillari ham mavjud. 📑 Run4j Quick start videolar rejasi: 1. Quickstart — “Hello, Run4j!” 2. Webhook → Script (GET/POST/PUT/DELETE) 3. Database Query (PostgreSQL) 4. Scheduled / Cron Jobs 5. Using Managers (RunContext, Nexus, ScriptManager, DataSourceManager, EmailMan…
👍6
Showing the 12 most recent of 20 posts we hold for @run4j. 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.
Citation-graph rank — 136,597 of 1,624,904entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Named by 1 registered channel — 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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“Run4j” (@run4j), 78 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/run4j.
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.