Un conflicto por tickets

Channel
Digital Harbor Bolivia 🚀
@digitalharborbolivia
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
280subscribers
-3 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 | -1001503490510 |
|---|---|
| Type | Channel |
| Username | @digitalharborbolivia |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/digitalharborbolivia |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 17:38 | 280 | -1 |
| 16 Aug 2026, 03:55 | 281 | -1 |
| 8 Aug 2026, 08:31 | 282 | no change |
| 8 Aug 2026, 04:23 | 282 | -1 |
| 7 Aug 2026, 20:53 | 283 | first reading |
Engagement
19 posts held, back to 18 April 2023 — 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 19 posts for this entry, the most recent from 3 March 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 46s
- Average length
- 46s
Measured directly from 1 video 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
41 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 56.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 23 | 56.1% | |
| 💯 | 8 | 19.5% | |
| 🏆 | 5 | 12.2% | |
| 🤩 | 4 | 9.76% | |
| 👌 | 1 | 2.44% |
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 19 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 41reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 18 April 2023 to 3 March 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
The owner of this channel has been inactive for the last 18 months. If they remain inactive for the next 7 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
Channel photo updated
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 19 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
Si, es cierto que cambiamos nuestra imagen pues... Nos encontramos en plena #rewowlucion por que estamos mejorando la forma en la que se utilizan las aplicaciones empresariales... 🤩🤩🤩 ...Y tú puedes ser parte de esto. 💥 Únete a nuestro equipo, tenemos las siguientes vacantes: - Full Stack Developer (Angular, Java + Spring Boot) - Tech Lead - Qa Lead - Qa Manager - DBA - Technical Project Manager - UX/UI Designer …
👍1
Channel photo updated
Viernes, San Juan, la noche mas fría del año y estas son las vacantes en DH: - Full Stack Developer (Angular, Java y Springboot) - QA Automation (Java, Cucumber, Selenium) - UX/UI Designer (Figma, AdobeXD, Adobe Illustrator, HTML, CSS) ⚠️ Recuerden: 👉🏼 Posiciones DEV dentro de Bolivia 👉🏼 Minimo 2 años de experiencia 👉🏼 Vacantes con inglés básico hasta avanzado 👉🏼 Project Manager en LATAM Manda tu CV a talent.recr…
Ya casi acaba la semana y como siempre, Digital Harbor esta buscando los mejores talentos 🚀🚀🚀 Les dejo las vacantes: - Full Stack Developer (Angular, Java, Springboot) (Javascript, Typescript). - QA Automation (Java, Selenium, Cucumber). - Tech Lead - QA Lead - Architect ⚠️ Recuerden: 👉🏼 Posiciones DEV dentro de Bolivia 👉🏼 Minimo 2 años de experiencia 👉🏼 Vacantes con inglés básico hasta avanzado Manda tu CV a ta…
👍4
Estamos en busca de un Database Administrator DBA 🚀🚀🚀 Requisitos: 👉🏼 + 4 años diseñando, administrando y manteniendo base de datos en MySQL y MSSQL 👉🏼 + 4 administrando y manteniendo bases de datos no relacionales (Mongo, Elastic Search) 👉🏼 Inglés avanzado 👉🏼 Experiencia en SQL y NoSQL Envía tu CV a ✉ [email protected] o contacta a una de las reclutadoras, nuestros números estan anclados al canal.
👍2
¡Feliz lunes a todos! 🚀🚀🚀 Les paso nuestras vacantes: 👩🏼🚀👩🏼🚀👩🏼🚀 - Fullstack Developer (angular Java) - Tech Lead - QA Engineer (Manual - Automation) - QA Lead - Project Manager - Software Architect - UI/UX Designer - DBA (Administrador de base de datos) ⚠️ Recuerden: 👉🏼 Posiciones DEV dentro de Bolivia 👉🏼 Minimo 2 años de experiencia 👉🏼 Vacantes con inglés básico hasta avanzado Manda tu CV a talent.recruitment…
¡Atención #LaPaz! 🚡 Estamos en busca de un Asistente de Seguridad que quiera un nuevo desafío y trabajar en un ambiente laboral WOW 😎 👨🎓 Si eres bachiller o tienes formación a nivel técnico en carreras administrativas o ramas afines ¡Esta es tu oportunidad! 📎 Responsabilidades: • Atención en recepción • Control de asistencia de colaboradores y visitantes • Envío y recepción de encomiendas • Gestión de compra de s…
¡Para todos los locos creativos de la tecnología, tenemos un evento WOW! 🚀🚀🚀 No te pierdas de este Meetup con la comunidad IDF Cochabamba este sábado 6 de Mayo a las 10:00 am en las oficinas de #DH 🗓️ MAÑANA! 📢📢📢 Se hablará sobre los sistemas de diseño, como usarlos, cuando y porque se usan en diseño de interfaces. No olvides inscribirte ⬇️ https://lnkd.in/d3n9Dhgq Link del evento ⬇️ https://fb.me/e/127fQTD5r Te…
👍2
Showing the 12 most recent of 19 posts we hold for @digitalharborbolivia. 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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Digital Harbor Bolivia 🚀” (@digitalharborbolivia), 280 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/digitalharborbolivia.
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.