biztrac. BETA
COMPANY REGISTER PROFILE
827533572 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other personal service activities n.e.c.

LABORATORIO AS

Org. no. 827533572 Limited company (AS) Oslo Incorporated 2021 Active
Revenue 2025 NOK 8,000
Operating profit NOK −1,000
Equity NOK 89,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1k kr).

LABORATORIO AS is registered as a limited company in Oslo, Oslo with organisation number 827533572. The business is classified under other personal service activities n.e.c. (NACE 96.990). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Matforedling. Catering tjenester. Detaljhandel med mat etter bearbeiding. Matlaging og salg av mat på restauranter, arrangementer og i et privat hjem.”. The most recent filed accounts, for the 2025 financial year, show NOK 8,000 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 8,000
▼ −24 %
Operating profit
NOK −1,000
▼ −143 %
Equity
NOK 89,000
▼ −1 %
Est. value
NOK 51,000

Financial health · 2025

Liquidity
27.65
Very good
Current assets ÷ current liabilities
Profitability
-1.1%
Not satisfactory
Return on total assets
Solidity
96.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LABORATORIO AS?

LABORATORIO AS
NOK 8,000 rev. · NOK −1,000 profit

LABORATORIO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LABORATORIO AS

Who owns LABORATORIO AS?

Petros Tsetso is the largest registered owner, with 100.0%.

What is the revenue of LABORATORIO AS?

LABORATORIO AS had revenue of NOK 8,000 in 2025.

Where is LABORATORIO AS based?

LABORATORIO AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.