Summary

  • Paraguay's CONATEL register identifies Roberto Adriano Dahmer Mariano under resolution 2218/2022, with GPON, a five-year term ending in October 2027, and service-location entries that can be compared across records dated 2024, 2025, and 2026.
  • DINAPI's TES TELECOM record and the public records for AS273063 add distinct trademark, number-resource, measurement, and routing views; those views document visibility but do not reveal how many people use a service or how they experience it.
  • The official name order differs from the display name Dahmer Mariano Roberto Adriano. The records are joined here only inside the specific Paraguay, CONATEL, TES TELECOM, and AS273063 context.
  • The documentary value lies in the alignment of several record types. None of them, alone or together, supplies a complete business biography or a basis for judging commercial outcomes.

A public record assembled in layers

This profile begins with a simple observation: no single document tells the whole story. The CONATEL entries identify a named operator in a national telecommunications register. The DINAPI document supplies a separate record for the TES TELECOM mark. LACNIC identifies the autonomous-system resource AS273063, while APNIC Labs and RIPEstat provide measurement and routing views. RPKI Report and PeeringDB add further public technical context. Each record answers a different question, and the combined picture is useful only when those questions remain separate.

CONATEL is the administrative anchor. It is the place where the official name order, resolution number, term, technology field, and service-location entries appear together. DINAPI helps explain why TES TELECOM belongs in the same bounded account. The number-resource and observability records show that AS273063 has a public technical identity beyond the administrative documents. This is a chain of legibility rather than a single narrative of achievement.

That distinction shapes the entire account. A register entry is evidence that an entry exists and contains specified fields. A trademark record is evidence of a mark record. An autonomous-system record is evidence of a network-number identity. A measurement page is evidence of population-level visibility. Combining them can clarify the record, but it cannot turn one type of evidence into another.

The two forms of the name

The display name in this profile is Dahmer Mariano Roberto Adriano. CONATEL uses Roberto Adriano Dahmer Mariano. Name-order differences are common in administrative material, but they must still be handled carefully. The connection here is not based on a loose similarity. It is limited to records that also share the Paraguayan telecommunications setting and, where relevant, the specific references to resolution 2218/2022, TES TELECOM, or AS273063.

This boundary matters because public databases can contain people with similar names, different ordering conventions, or incomplete identifying context. A broad search could easily pull unrelated records into one account. The safer method is to require a second point of alignment. In the CONATEL documents, that alignment comes from the same resolution, dates, term, technology field, and locations. In the DINAPI and network records, it comes from the separately established TES TELECOM and AS273063 context.

The alternate order is therefore not treated as a second person or as a biographical detail. It is a record-management fact that helps readers follow the documents. Nothing outside this bounded set is merged into the profile. The approach preserves the usefulness of the official records while avoiding claims about similarly named people elsewhere.

CONATEL as the administrative anchor

Paraguay's Comisión Nacional de Telecomunicaciones, CONATEL, maintains the national telecommunications-services register used in this account. Three checked versions contain a consistent row for Roberto Adriano Dahmer Mariano. The June 2024 document places that row on page 20. The July 2025 document places it on page 27. The March 2026 document carries the same identifying fields on page 9. The layout and row numbering change, but the central fields remain recognizable.

Across the three versions, the records show resolution 2218/2022, a resolution date in October 2022, a five-year term, an expiration date in October 2027, and GPON as the technology field. The listed service locations also provide a dated view that can be compared from one version to another. Later versions carry more location names and a reference to resolution 1300/2025.

The register is valuable because it brings person, authorization, time, technology, and geography into one administrative frame. At the same time, it is still a register. It does not describe day-to-day operations, user experiences, finances, or the reasons behind individual decisions. Its strength is precision about the fields it contains, not breadth about everything surrounding them.

The June 2024 entry

The June 2024 CONATEL document is titled "Registro Nacional de Servicios de Telecomunicaciones - Servicios de acceso a internet y transmisión de datos." Its relevant row is numbered 190 and identifies Roberto Adriano Dahmer Mariano. The row lists resolution 2218/2022, dated 06.10.2022, a five-year term, an expiration date of 25.10.2027, and GPON. Guarambare and Repatriación appear in the service-coverage field.

Those fields establish a useful baseline. They show what the register recorded at that date and provide exact points for comparison with later editions. The row number itself is only a position in that edition of the document; it should not be interpreted as a ranking or an indication of size. Likewise, the appearance of two locations is a statement about the register's listed field, not a count of installations, users, or completed connections.

The relevant information is best read as a dated administrative snapshot. It gives the profile a specific starting point and establishes the exact official name order used in the later records.

The July 2025 entry

The July 2025 CONATEL edition carries a closely matching row, numbered 191. It again identifies Roberto Adriano Dahmer Mariano and repeats resolution 2218/2022, the October 2022 date, the five-year term, the October 2027 expiration, and GPON. The listed service locations now include Guarambare, Repatriación, Caaguazú, Mauricio Jose Troche, and Juan Manuel Frutos.

This later entry also contains "SI" in the internet-content field and refers to resolution 1300/2025. The locations associated with that reference are Mauricio Jose Troche, Juan Manuel Frutos, and Repatriacion. These are documentary fields, not an invitation to reconstruct a larger operational story. The reliable statement is that the later register includes the additional names and resolution reference.

Compared with the 2024 version, the July 2025 document provides evidence of a broader set of locations in the register. It does not specify how connections were distributed within those places, how many people used them, or what the experience was. The value of the comparison is administrative continuity plus a dated change in the listed fields.

The March 2026 entry

The March 2026 CONATEL RNST document provides the latest exact row examined for this profile. It again lists Roberto Adriano Dahmer Mariano, resolution 2218/2022, the October 2022 resolution date, a five-year term, an expiration date of 25 October 2027, and GPON. It repeats the five place names found in the July 2025 version and again carries the resolution 1300/2025 reference with Mauricio Jose Troche, Juan Manuel Frutos, and Repatriacion.

The March 2026 document's significance comes from continuity across time. The name, principal resolution, term, expiration, and technology fields align with the earlier versions. The service-location field remains broader than it was in June 2024.

Continuity in a register should be described with care. It means that the same core information appears in the checked editions. It does not, by itself, establish what happened between editions or after the latest date. The March 2026 row is therefore a later public snapshot, not a real-time account. Its role is to confirm that the central administrative identity remained visible in the checked record family.

What changed and what remained constant

Comparing the three CONATEL records reveals two kinds of information. First, several fields remain constant: the official name order, resolution 2218/2022, the October 2022 date, the five-year term, the October 2027 expiration, and the GPON technology label. Second, the listed geography changes. The 2024 row names Guarambare and Repatriación, while the 2025 and 2026 rows also name Caaguazú, Mauricio Jose Troche, and Juan Manuel Frutos.

This is a modest but meaningful documentary comparison. It shows continuity in the principal administrative fields and a later broadening of the location list. It also provides a reason to cite dates whenever describing the record. A statement drawn from the 2024 edition may not capture every field shown in 2025 or 2026, while the later versions should not be projected backward without qualification.

The documents do not explain the process behind each change. They do not say how the additional locations were selected, when any physical work occurred, or what practical reach followed. The comparison is strongest when it stays at the level of the recorded fields. That is enough to establish a chronology without adding a story that the documents do not contain.

Reading the location names correctly

Place names are among the most concrete elements in the CONATEL rows, but they are also easy to overstate. Guarambare and Repatriación appear in the 2024 entry. Caaguazú, Mauricio Jose Troche, and Juan Manuel Frutos join them in the later checked versions. Resolution 1300/2025 is associated in the register with Mauricio Jose Troche, Juan Manuel Frutos, and Repatriacion.

The proper description is that these names appear in the service-coverage fields of the dated records. The documents provided for this profile do not supply maps, address-level boundaries, connection counts, or measurements of actual use within those places. A location in a register is not the same thing as a complete map of infrastructure or a claim that every part of that location was reached.

Keeping this distinction visible protects the value of the record. Readers can understand that the administrative footprint listed in the document broadened after 2024 without being asked to assume more. The place names make the profile specific to Paraguay and distinguish it from a generic discussion of a small network. Their evidentiary role is geographic identification within a dated official entry.

Resolution 2218/2022 as a recurring identifier

Resolution 2218/2022 is the strongest recurring administrative identifier across the checked CONATEL documents. The 2024 and 2025 versions show the date as 06.10.2022, while the 2026 version renders it as 6/10/2022. The formatting differs, but the resolution number and date align. That repetition helps connect the rows across editions even as row numbers and layouts change.

The resolution should not be made to carry more meaning than the records provide. It identifies the administrative basis shown in the register. The supplied materials do not include the full text of the resolution, so this profile does not describe clauses, obligations, findings, or procedural history that cannot be checked here. It reports the number, date, term, expiration, and associated fields exactly as the register presents them.

Resolution 1300/2025 has a narrower role. It appears in the later rows alongside specified locations. The record supports noting that reference and its associated place names. It does not support a broader interpretation of why the resolution was issued or what happened outside the listed fields. Treating both numbers as precise documentary anchors keeps the account verifiable.

The five-year term and October 2027 date

Each checked CONATEL version lists a five-year term and an expiration date in October 2027. The 2024 and 2025 documents render the date as 25.10.2027, while the 2026 document uses 25/10/2027. As with the resolution date, the change is typographic rather than substantive within the record.

These dates define the temporal frame shown by the register. They do not guarantee what the entry will look like in the future, and they do not establish events that may occur before or after the listed date. The records are best understood as dated statements by the register, not predictions. Any later account would need to check a later official edition rather than assume continuity.

The term also helps distinguish this profile from a timeless description. Telecommunications records change, and a date-sensitive account should make that visible. Here, the checked sequence runs from June 2024 through March 2026, while the term field points to October 2027. That is the full temporal statement supported by the materials. No conclusion about renewal, continuation, or later status is made.

GPON as a register field

GPON appears consistently in the technology field of all three CONATEL entries. In this profile, it is treated exactly that way: as the technology label recorded by the regulator. The documents support connecting GPON to the named operator and listed service locations within the administrative record. They do not provide a technical inventory or a performance assessment.

This restraint is important because a familiar access-network term can invite a much larger narrative. The checked materials do not describe equipment brands, network design, capacity, installation dates, household reach, maintenance practice, or measured results. They also do not show whether every listed place had the same configuration. None of those details should be supplied by assumption.

The GPON field is nevertheless meaningful. It identifies the access technology category used in the official rows and links the administrative record to a recognizable infrastructure context. Together with the internet and data-services title of the register, it explains why the person and location entries belong in a network profile. The most accurate formulation remains simple: CONATEL's checked records list GPON for Roberto Adriano Dahmer Mariano.

TES TELECOM in the trademark record

The TES TELECOM layer comes from Paraguay's Dirección Nacional de Propiedad Intelectual, DINAPI. Its public visualization supplies trademark evidence linked to the same bounded person-name context. This record gives the service-facing label a formal place in the documentary chain.

A trademark record has a specific function. It helps identify a mark and connect that mark to a filing context. It does not describe the entire history of an operation, the extent to which a name was used, or the results associated with it. For that reason, TES TELECOM is presented here as the mark appearing in the public record, not as a claim about commercial standing.

The DINAPI document also strengthens the distinction between this subject and unrelated records. CONATEL supplies the named telecommunications entry; DINAPI supplies TES TELECOM; the network records supply AS273063. When these elements are kept in their proper roles, the profile becomes more specific without becoming more speculative. Private filing details are unnecessary to that account and are not reproduced.

AS273063 as a number-resource identity

AS273063 is the technical identifier at the center of the network portion of this profile. The LACNIC RDAP record supplies allocation and registry context for the autonomous-system number. APNIC Labs provides a population-level visibility view, and RIPEstat provides AS overview and routing-status views. These sources make the network resource publicly legible without revealing the complete operation behind it.

An AS number is not a substitute for a business description. Its presence in a registry or routing view does not state how many people buy a service, what those people experience, or what financial results follow. It is a number-resource identity that can be observed through public technical systems. That is both useful and limited.

The AS273063 layer matters because it extends the account beyond static administrative files. CONATEL shows the operator and GPON context; DINAPI shows the TES TELECOM mark; the network sources show that AS273063 has separate registry and observability records. The connection among those layers is the story. No single technical page is treated as person-level proof on its own.

LACNIC RDAP and the registry layer

The LACNIC RDAP endpoint is the primary number-resource reference in the source set. It identifies AS273063 in a structured registry context. For this profile, the relevant information is the autonomous-system resource and its place in the broader evidence boundary.

RDAP data can include private administrative details, but those fields are not needed here. Removing them does not weaken the network account; it keeps the focus on the public resource identity.

The RDAP record also has a clear evidentiary limit. It should not be used alone to connect every other record to the person. That connection depends on the CONATEL and DINAPI layers already described. Used in that sequence, RDAP contributes a precise technical identifier. Used without the other layers, it would risk turning a people profile into a registry summary. The layered approach preserves both relevance and privacy.

APNIC Labs and population-level visibility

APNIC Labs offers a separate measurement view. The evidence set uses this page for AS population visibility in Paraguay and identifies AS273063 as measurable in that context. No numerical value is needed to establish the limited point that the autonomous system appears in the measurement view.

Population-level visibility must not be confused with customer data. A measurement system can observe signals associated with an AS without knowing the commercial relationship behind every observation. It does not provide a subscriber list, a user count for the operator, a service map, or an assessment of individual experience. The page therefore belongs in the technical-observability layer rather than the administrative or commercial layers.

This independent measurement view still adds substance. It shows that AS273063 is not present only in an allocation record. The number also appears in an external system designed to observe internet population visibility. That makes the network identity more legible while leaving many practical questions unanswered. The careful conclusion is visibility, not scale.

RIPEstat's AS overview

RIPEstat's AS overview endpoint provides another public view of the autonomous system. The overview belongs to the network-observability portion of the record. It can help a reader verify that AS273063 is recognized as a resource in a public technical data service.

The overview is not a substitute for CONATEL or DINAPI. It does not establish the full person-name relationship, the content of a Paraguayan telecommunications entry, or the meaning of the TES TELECOM mark. Those facts come from their respective administrative records. Conversely, the administrative records do not replace the technical overview. Each layer has its own evidentiary job.

This separation makes the combined account clearer. The AS overview supports a statement about public network identity. It does not support statements about the quality, reach, reliability, or economic significance of an access service. Readers can use the endpoint to inspect the current technical response, while remembering that such responses may change over time and should be dated when used.

Routing status as a changing observation

RIPEstat also provides a routing-status endpoint for AS273063. This source adds a view of the autonomous system in public routing data. It is a technical observation, not an administrative authorization and not a report about user experience.

Routing information is inherently time-sensitive. A response observed on one date may differ on another date as public routing data changes. The presence of a routing-status view is therefore best used to establish that AS273063 can be examined through a public technical service. Any claim about a specific current state would need a dated response and exact fields. This profile does not add details that are absent from the supplied evidence.

The distinction between visibility and evaluation remains central. A public routing view can show that a network resource is observable. It cannot tell a reader whether an access service met expectations, how widely it was used, or why a particular routing arrangement existed. The source is valuable precisely because it answers a narrower question with technical specificity.

RPKI Report and PeeringDB as supporting context

Two additional references complete the public network map. RPKI Report provides an AS273063 page, and PeeringDB provides an AS273063 profile. The evidence set treats the first as route-origin-authorization context and the second as network-service context.

Neither page is used as the sole basis for identifying the person or the TES TELECOM mark. They sit after the CONATEL, DINAPI, and LACNIC evidence in the hierarchy. The RPKI reference can help a technically interested reader locate public route-origin material. The PeeringDB reference can help locate a public network profile. No unrecorded status, relationship, facility, or exchange arrangement is asserted here.

This supporting role avoids a common error in network profiles: reading a community-maintained or technical page as a complete organizational biography. These pages add ways to inspect AS273063. They do not replace the official Paraguayan records or authorize conclusions about business outcomes. Their contribution is context and independent discoverability.

How the administrative and technical records align

The combined evidence can be visualized as four adjoining layers. The first is the CONATEL register, where the official name order, resolutions, term, GPON field, and locations appear. The second is the DINAPI record for TES TELECOM. The third is the LACNIC allocation and registry context for AS273063. The fourth consists of APNIC Labs, RIPEstat, RPKI Report, and PeeringDB, which provide measurement, routing, authorization, and network-profile views.

Alignment does not mean that every source repeats every fact. In fact, the value of the chain comes from their differences. CONATEL does not need to reproduce a routing-status response, and RIPEstat does not need to reproduce a trademark filing. The records become mutually informative because each supplies a distinct part of the same bounded infrastructure context.

The boundary remains strict: Paraguay, the named operator record, TES TELECOM, and AS273063. If a record lacks that alignment, it is not included merely because a name looks similar. This method produces a more reliable profile than a broad collection of loosely related search results. It also makes each statement easier to trace back to the record type that supports it.

Public visibility is not a measure of audience

Several sources in this profile describe visibility. APNIC Labs supplies population-level visibility; RIPEstat supplies AS and routing views; RPKI Report supplies route-origin context; PeeringDB supplies a network profile. It is tempting to combine those signals into a claim about the size or importance of an operation. The supplied records do not allow that step.

Visibility means that an identifier appears in a particular public system. It does not reveal the contractual relationship behind an observed connection, the number of paying users, the number of active lines, or the quality of an individual session. Different systems also measure or display different things. Their results should not be added together as though they were a single audience metric.

For the same reason, the CONATEL location list should not be combined with APNIC visibility to create an implied user total. One record lists administrative geography; the other offers population-level network measurement. The responsible account keeps them separate. Together they show that the subject is visible in both local administrative records and wider technical systems, which is a meaningful fact without numerical embellishment.

A natural-person operator in the public record

This case is notable because the CONATEL entry is organized around a person's name rather than only a corporate name. Roberto Adriano Dahmer Mariano is the form used in the register, while Dahmer Mariano Roberto Adriano is the display form used here. TES TELECOM supplies the associated mark context, and AS273063 supplies the network-resource context.

A person-centered administrative record does not turn this into a conventional biography. The supplied materials do not describe childhood, education, career chronology, personal beliefs, or reasons for entering telecommunications. Adding such material from assumption would weaken the profile. The subject is present because the name anchors a verifiable infrastructure record.

This also raises the importance of proportionality. The public interest lies in the telecommunications, trademark, and number-resource information. Private contact fields or unrelated personal details add no value to that account. By keeping the focus on the formal record, the profile can document a person-level infrastructure identity without converting administrative data into an invasive portrait.

Privacy without losing documentary value

The source set establishes a clear privacy boundary. Private administrative, identifying, and contact details are excluded. Some public databases may expose such fields, but public availability alone does not make them necessary to a documentary article.

Nothing essential is lost by omitting them. Readers can understand the identity boundary through the two name orders, Paraguay, resolution 2218/2022, TES TELECOM, and AS273063. They can verify the administrative and technical references through the canonical URLs. Personal contact details would not improve the explanation of GPON, the dated service-location fields, or network visibility.

This approach also avoids implying that a contact listed for an administrative purpose has a broader public role. Registers are designed for specific institutional functions. A documentary profile can cite the institutional record while selecting only the fields relevant to the public subject. That is a more accurate use of the material than reproducing every field simply because it is present.

Avoiding same-name errors

Name matching is one of the largest risks in a profile assembled from several databases. The order Roberto Adriano Dahmer Mariano is distinctive in the CONATEL entries, but a name alone is still not enough to merge unrelated records. The evidence here requires additional alignment with Paraguay and with the CONATEL, TES TELECOM, or AS273063 context.

The three CONATEL versions are joined through repeated fields: the same official name order, resolution 2218/2022, October 2022 date, five-year term, October 2027 expiration, and GPON label. The TES TELECOM record is included within the separately established person-name boundary. The AS273063 records are included within the same bounded network context. Records outside those anchors are not part of this account.

This method is intentionally conservative. It may leave some potentially related material unused, but it sharply reduces the risk of attributing another person's activity to the subject. A public profile is stronger when every connection can be explained than when it appears comprehensive because it has collected every similar-looking result.

What the records do not answer

The documents answer questions about identity, administrative entries, a mark, an autonomous-system resource, and public technical visibility. They do not answer many other questions that readers might reasonably ask. They do not provide a count of people using a service, a detailed network map, financial statements, independent experience studies, support records, or a complete organizational history.

They also do not explain personal intent. A resolution number and a trademark record cannot reveal why an individual chose a particular technology, location, name, or network arrangement. Technical visibility cannot establish the practical effect of a service in a community. An absence of such evidence is not a negative finding; it is simply the edge of the available record.

Recognizing that edge is essential to a neutral account. It prevents official documents from being turned into praise, criticism, or speculation. The strongest conclusion is narrower: several public systems consistently identify a specific Paraguayan telecommunications subject, and those systems can be read together while preserving the limits of each.

Dates, snapshots, and future changes

Every record in this profile is a snapshot. The CONATEL sequence is especially clear: June 2024, July 2025, and March 2026. The central fields remain stable across those dates, while the listed locations broaden after 2024. The term field points to October 2027, but that future date should not be treated as proof of what a later register will show.

Technical references are also time-sensitive. RDAP data, routing views, population measurements, route-origin material, and network profiles can change. A reader revisiting the links later may see a different response from the one available when this account was prepared. That is normal for living public systems.

The practical lesson is to cite both the record and the date of observation. Historical versions should remain historical rather than being silently replaced by current data. If a future CONATEL edition changes a field, it should be described as a later development, not used to rewrite what the 2024 or 2025 documents contained. This dated approach keeps the account maintainable and transparent.

Verifying the record independently

Readers can verify the central administrative sequence by opening the three CONATEL PDFs and searching for the official order Roberto Adriano Dahmer Mariano or resolution 2218/2022. The June 2024 row appears on page 20, the July 2025 row on page 27, and the March 2026 row on page 9. The row numbers and page layouts differ, so the repeated resolution and date fields are useful cross-checks.

The TES TELECOM layer can be checked through the DINAPI visualization. AS273063 can then be inspected separately in LACNIC RDAP, APNIC Labs, and RIPEstat. RPKI Report and PeeringDB offer additional public technical references. This sequence mirrors the evidence hierarchy: administrative identity first, mark context second, number-resource identity third, and broader observability last.

Independent verification should preserve the same privacy boundary. There is no need to copy contact or address fields into notes or public discussion. The relevant checks concern the name, resolutions, dates, technology label, locations, mark, AS number, and non-personal technical context.

A measured interpretation of the whole record

Taken as a whole, the evidence supports a measured interpretation. Dahmer Mariano Roberto Adriano, appearing in CONATEL's official order as Roberto Adriano Dahmer Mariano, is associated in the checked Paraguayan register with resolution 2218/2022, a five-year term ending in October 2027, GPON, and named service locations. Later rows include a wider location list and reference resolution 1300/2025.

DINAPI adds the TES TELECOM mark record. LACNIC adds the AS273063 number-resource context. APNIC Labs and RIPEstat make the AS visible through independent measurement and routing services, while RPKI Report and PeeringDB provide additional technical reference points. The layers align without becoming identical.

This is enough for a substantive public-record profile. It is not enough for a complete biography or a verdict about an enterprise. The absence of those broader conclusions is a strength, not a deficiency. It keeps the account close to the evidence and gives readers a clear map for checking each part themselves.

The same structure also makes later updates straightforward. A new CONATEL edition can be compared with the three dated rows without changing what those earlier documents say. A changed registry or routing response can be recorded as a later observation. A separate administrative document can be added to the institution that issued it. This preserves chronology and prevents new material from being projected backward. For now, the record remains deliberately and clearly bounded: one named subject, one Paraguayan telecommunications context, one mark, one autonomous-system number, and a defined set of public technical references.

Public records and network references