Mobility · Berisso

# Traffic fines in Berisso: what the API returns and what the data shows

Which fines Berisso issues between the port and Montevideo avenue, what our data from the last year shows and how a container fleet queries the municipal court by plate.

![](/img/autores/francisco-orione/photo-240.ff6c48f047e6.webp)By [Francisco Orione](https://apinitro.com/en/authors/francisco-orione/)September 15, 2026

![A street of muted-colour tin houses with a wooden pier in the background](/img/articulos/ar-traffic-fines-ar-b-berisso/hero-1200.60931e8d304b.webp)

Jurisdiction

Berisso (Buenos Aires) · [Buenos Aires](https://apinitro.com/en/articles/traffic-fines-buenos-aires-province/) · Argentina

Berisso is the partido of the La Plata port and the riverside: Montevideo, 60 and Génova avenues connect the city with La Plata and Ensenada, and along them container trucks, industrial-zone transport and the cars of a partido that grew around the meatpacking plants come and go. Municipal fines are issued by the partido; provincial ones coexist on the same plates.

## Context and authority

Like every partido in Buenos Aires, it applies the [National Traffic Law 24.449](https://www.argentina.gob.ar/normativa/nacional/ley-24449-818/texto) through the provincial adhesion: fixed-unit amounts, a two-year limitation for minor offences and five for serious ones, and a defence before the court that issued the fine. Provincial fines are covered in the [Buenos Aires article](https://apinitro.com/en/articles/traffic-fines-buenos-aires-province/).

The municipal misdemeanour court rules on Berisso fines: lanes and manoeuvres on Montevideo avenue and at the port approaches, red lights and right of way at the camera-equipped intersections downtown, and parking in the commercial area. A defence is filed with the court within the period set by the notice.

## What the API returns for this jurisdiction

A plate lookup in Berisso walks the Berisso municipal misdemeanour court together with the integrated provincial sources of Buenos Aires, and returns each fine with the authority that issued it:

-   Authority and fine number exactly as each court publishes them.
-   Date, location when reported and description of the infraction.
-   Amount, status and payment conditions published by that court.
-   Downloadable payment slip when one exists.
-   Coverage per source and partial-result flag.

The response splits the result by source: the Berisso court and the provincial sources answer separately, and the partial-result flag shows whether any failed to answer.

## What the data shows

Proprietary data**Berisso**September 1, 2025 – August 31, 2026

Fines offering voluntary early payment

100%

Median age of fines without a recorded resolution

210 days

Median amount band

ARS 100,000 – ARS 250,000

Mix by infraction category

1.  Red light and right of way43%
2.  Lanes and manoeuvres55%
3.  Other infractions2%

Monthly distribution of fines

1.  Jan5%
2.  Feb7%
3.  Mar20%
4.  Apr8%
5.  May6%
6.  Jun9%
7.  Jul3%
8.  Aug1%
9.  Sep2%
10.  Oct14%
11.  Nov12%
12.  Dec13%

Sample: 100–500 fine records, 50.000+ lookups · [See the data methodology](https://apinitro.com/en/data-methodology/)

Lookups with a Berisso fine did not reach the publication floor of the [data methodology](https://apinitro.com/en/data-methodology/), so we do not publish that share; the sample of fines observed is between one hundred and five hundred. What it does show is a concentrated mix: lanes and manoeuvres explain more than half of the fines and red lights almost all the rest.

The median amount band is ARS 100,000 – ARS 250,000 and the median age of open fines is 210 days.

100% of the fines offered voluntary payment at lookup time: every one observed. In Berisso, looking up in time means paying with a discount.

## Case study: fleets that look up plates in Berisso

Proprietary data**Fleet cohort**September 1, 2025 – August 31, 2026

Fleet accounts in the sample

50

Distinct plates looked up by fleets

2,040

Sample: 100–500 fine records, 50.000+ lookups · [See the data methodology](https://apinitro.com/en/data-methodology/)

The fleet cohort, 50 accounts with twenty or more plates and 2,040 plates in total, had fewer than fifty lookups with a Berisso fine, the floor the [data methodology](https://apinitro.com/en/data-methodology/) requires to publish a share; the figure exists, but it is not published below that threshold.

For a container transport company entering the port along Montevideo avenue, the reading is simple: the fines are for manoeuvres and red lights, not speeding, and all of them are paid with a discount if they show up in time. A plate lookup at the close of each month, with the result stored, assigns the fine to the driver and collects the discount.

## How to integrate

Each plate is sent in a POST, with the jurisdictions to include if you do not want to query all of them. The response accepts the job and the result is retrieved by status lookup or arrives by webhook once the sources finish answering. The [vehicle lookup quality](https://apinitro.com/en/articles/vehicle-data-quality/) guide explains how to handle partial results and the [API page](https://apinitro.com/en/apis/traffic-fines-argentina/) details access.

JSONIllustrative example, not a contract.

```json
{
  "plate": "ABC123",
  "jurisdictions": [
    "AR-B-berisso"
  ]
}
```

Read the result per source: the municipal court and the provincial source answer separately, and the partial-result flag says whether any failed to answer. The [vehicle lookup quality](https://apinitro.com/en/articles/vehicle-data-quality/) guide explains how to handle that case.

## Limits and considerations

-   Fines at the port approaches may belong to Ensenada or the province, not Berisso; the response names the authority of each.
-   Fixed-unit amounts are converted at the value current at the source; the final amount is set by the authority at the time of payment.
-   Proprietary data comes from user lookups, not from a registry: the share of fines is skewed towards suspect plates.
-   A source that does not answer is reported as such, never as an absence of infractions.
-   The API neither pays fines nor handles defences; it delivers information to decide.

## Sources and further reading

-   [Municipalidad de Berisso](https://www.berisso.gob.ar/)
-   [Ley Nacional de Tránsito 24.449 — texto actualizado](https://www.argentina.gob.ar/normativa/nacional/ley-24449-818/texto)
-   [Agencia Nacional de Seguridad Vial — Consulta nacional de infracciones](https://consultainfracciones.seguridadvial.gob.ar/)

Related API

## [Argentina traffic fines API](https://apinitro.com/en/apis/traffic-fines-argentina/)

Bring vehicle fine checks into fleet operations, vehicle transactions and document review workflows.

[Ask about this API](https://apinitro.com/en/contact/?api=ar.mobility.traffic-fines&ref=article:ar-traffic-fines-ar-b-berisso)

## Related articles

[![](/img/articulos/ar-traffic-fines-ar-b/hero-640.e7b8a039b11b.webp)

Mobility

## Traffic fines in Buenos Aires Province: what the API returns and what the data shows

Two layers of authorities, one plate: how to look up provincial and municipal fines through the API and what a year of our data shows.

Read article ↗](https://apinitro.com/en/articles/traffic-fines-buenos-aires-province/)

[![](/img/articulos/ar-traffic-fines-ar-b-florencio-varela/hero-640.58d8ee258c32.webp)

Mobility

## Traffic fines in Florencio Varela: what the API returns and what the data shows

Which fines Florencio Varela issues on Route 53 and San Martín avenue, what our data from the last year shows and how a horticultural fleet queries the municipal court by plate.

Read article ↗](https://apinitro.com/en/articles/traffic-fines-florencio-varela/)

[

Mobility

## How to assess the quality of a vehicle lookup

A useful vehicle lookup explains what was observed, where and when. These questions help teams turn records into clear product decisions.

Read article ↗](https://apinitro.com/en/articles/vehicle-data-quality/)

[

Integrations

## Asynchronous APIs: retry without duplicating work

A connection can fail after work has already started. Designing around the operation makes recovery clearer for users and integrations.

Read article ↗](https://apinitro.com/en/articles/asynchronous-api-retries-without-duplicate-work/)

[← All articles](https://apinitro.com/en/articles/)
