Total revenue
86,636 RON
13 client authorities · paid between 2018 and 2026
Direct purchases
82,664 RON
194 purchases
Offline purchases
3,972 RON
3 purchases
Tenders
0 RON
0 contracts
Won without competition
—
Below the minimum of 5 lots won for indicator 5
Won at the estimated value
—
Below the minimum of 5 lots won for indicator 7
Dependence on the main client
54.6%
Main client: UNIVERSITATEA DE MEDICINA FARMACIE STIINTE SI TEHNOLOGIE GEORGE EMIL PALADE DIN TARGU MURES
National median: 30.2%
Ranked 6,650 of 41,897
The first two figures show what part of the money won in tenders came from lots with a single offer, and from lots paid exactly at the estimated value. An association's contract is split evenly among members, as for indicators #05 and #07. The national rate is computed on the same money, for the whole country.
Risk indicators
None of the seven supplier indicators found a case here. #06, #08 and #09 are computed on authorities only, so they do not appear here. #10 counts the markets where the company is the largest supplier.
Revenue by year
The year is the one the money was paid in: the finalisation date for direct purchases and offline purchases, the contract date for tenders.
What it sells
The 12 largest CPV groups, out of 18; the other 6 are added into a single tile. A tender contract has no CPV code of its own, so its money goes to the notice's main code. For notices with several lots this is an approximation.
Who pays the company
The first share is of the company's revenue, the second of the authority's spending. The symbol beside an authority: indicator #04 flags the pair. Money with no authority in the data does not appear.
Each amount leads to the purchases it was computed from. For direct purchases and offline purchases the rows add up exactly to the figure; for tenders the notices the supplier won open, with the whole notice's value, not only its share.
- Direct purchases
- What the company was paid by this authority through direct purchases. The link opens exactly those purchases.
- Offline purchases
- What the company was paid by this authority through offline purchases.
- Tenders
- The company's share of the authority's tender contracts.
- Total
- The three streams added up: everything the company was paid by this authority.
- Of the company's revenue
- The part of the company's revenue that comes from this authority (captivity, in indicator #04)
- Of the authority's spend
- The part of everything the authority spent that went to this company
- Contracts
- How many direct purchases, offline purchases and tender contracts the two share.
- Period
- The first and last year the company was paid by this authority.
Latest sales
Latest direct purchases
See allLatest offline purchases
See all| SEAP no. | Contracting authority | CPV code | Date | Value |
|---|---|---|---|---|
| DAN2357479 | MUNICIPIUL TARGU MURES CUI: 4322823 | 34300000-0 | 13.01.2025 | 80 |
| Contract object: cruce ax volan ms10ala/ luminator frana | ||||
| DAN2350337 | JUDETUL MURES CUI: 4322980 | 34913000-0 | 30.12.2024 | 2,338 |
| Contract object: piese de schimb pentru autovehiculele din dotarea centrului militar judetean | ||||
| DAN2186121 | JUDETUL MURES CUI: 4322980 | 34913000-0 | 23.05.2024 | 1,554 |
| Contract object: piese de schimb pentru autovehiculele din dotarea centrului militar judetean mures | ||||
- SEAP no.
- The purchase's SEAP number, linked to its record on e-licitatie.ro.
- Contracting authority
- The authority that bought. The name leads to its profile.
- CPV code
- The CPV code: what was bought. Hover it for the name; a click filters the list on it and the codes below it.
- Finalisation date
- The finalisation date, that is, when the money was spent. The list is ordered by it and the year filter applies to it.
- Date
- The date of publication in SEAP.
- Value
- The value of the purchase, excluding VAT, rounded to the leu.
- Contract object
- The object of the purchase as the authority described it, on the line under the figures.
The same data, through the API
Every figure on this page comes from the public API, through the endpoints below. The parameters each one takes are in the documentation; each needs an access key.
/api/v1/suppliers/22491650/api/v1/suppliers/22491650/revenue/api/v1/suppliers/22491650/scores/api/v1/suppliers/22491650/benchmarks/api/v1/red-flags/by-supplier/22491650/api/v1/suppliers/22491650/years/api/v1/suppliers/22491650/cpv/api/v1/suppliers/22491650/clients/api/v1/suppliers/22491650/partners/api/v1/acquisitions/direct/api/v1/acquisitions/awards/api/v1/acquisitions/tenders