BIZTRAC BETA
Construction of residential and non-residential buildings

CRO TEAM AS

Org. no. 918765425 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 7.0m
Operating profit NOK 20,000
Equity NOK 126,000
Incorporated 2017
Employees 7
Share capital NOK 30,000

CRO TEAM AS is registered as a limited company in Oslo, Oslo with organisation number 918765425. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Byggetjenester herunder kjøp og videresalg av byggevarer, utleie, formidling og opplæring av personell til næringsvirksomhet utenfor eget selskap, renholdstjenester malertjenester samt alt som hører naturlig inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.0m in revenue and NOK 20,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.0m
Operating profit
NOK 20,000
Equity
NOK 126,000
Est. value
NOK 123,000

Financial health · 2025

Liquidity
0.93
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.6%
Weak
Equity as a share of total capital

Who owns CRO TEAM AS?

KRUNOSLAV LUKINOVIC
CRO TEAM AS
NOK 7.0m rev. · NOK 20,000 profit

CRO TEAM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CRO TEAM AS

Who owns CRO TEAM AS?

KRUNOSLAV LUKINOVIC is the largest registered owner, with 50.0%.

What is the revenue of CRO TEAM AS?

CRO TEAM AS had revenue of NOK 7.0m in 2025.

Who is the general manager of CRO TEAM AS?

Kristijan Mihac is registered as general manager of CRO TEAM AS.

Where is CRO TEAM AS based?

CRO TEAM 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 15.06.2026.

Report a problem

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