BIZTRAC BETA
Development of building projects

CRESCO EIENDOM AS

Org. no. 987579900 Limited company (AS) Nordre Follo Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 46.5m
Operating profit NOK −971,000
Equity NOK 8.8m
Incorporated 2004
Employees 5
Share capital NOK 150,000

Signals

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

CRESCO EIENDOM AS is registered as a limited company in Nordre Follo, Akershus with organisation number 987579900. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2004 and has 5 registered employees. Registered share capital is NOK 150,000, divided into 1500 shares. The company's stated purpose is: “Prosjektere, utvikle og eie eiendom samt tilby tjenester innen el-, VVS-, ventilasjon-, snekker- og murerarbeid. Selskapet skal også kunne drive forretningsvirksomhet gjennom handel og investering i aksjer og andre eiendeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 46.5m in revenue and NOK −971,000 in operating profit.

Key figures · 2025

Revenue
NOK 46.5m
Operating profit
NOK −971,000
Equity
NOK 8.8m
Est. value
NOK 75.7m

Financial health · 2025

Liquidity
2.05
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
51.1%
Very good
Equity as a share of total capital

Who owns CRESCO EIENDOM AS?

ANDREAS ULMO
CRESCO EIENDOM AS
NOK 46.5m rev. · NOK −971,000 profit

CRESCO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CRESCO EIENDOM AS

Who owns CRESCO EIENDOM AS?

ANDREAS ULMO is the largest registered owner, with 100.0%.

What is the revenue of CRESCO EIENDOM AS?

CRESCO EIENDOM AS had revenue of NOK 46.5m in 2025.

Where is CRESCO EIENDOM AS based?

CRESCO EIENDOM AS has its business address in Trollåsen.

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.