BIZTRAC BETA
Rental and operating of own or leased real estate

CETUS EIENDOM AS

Org. no. 925171085 Limited company (AS) Alta Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 625,000
Operating profit NOK 186,000
Equity NOK 11.3m
Incorporated 2020
Share capital NOK 10.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

CETUS EIENDOM AS is registered as a limited company in Alta, Finnmark with organisation number 925171085. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 10.0m, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg, utleie og drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 625,000 in revenue and NOK 186,000 in operating profit.

Key figures · 2025

Revenue
NOK 625,000
Operating profit
NOK 186,000
Equity
NOK 11.3m
Est. value
NOK 8.3m

Financial health · 2025

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

Who owns CETUS EIENDOM AS?

COSMOS INVEST AS
CETUS EIENDOM AS
NOK 625,000 rev. · NOK 186,000 profit

CETUS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CETUS EIENDOM AS

Who owns CETUS EIENDOM AS?

COSMOS INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of CETUS EIENDOM AS?

CETUS EIENDOM AS had revenue of NOK 625,000 in 2025.

Who is the general manager of CETUS EIENDOM AS?

Bjørn Ove Thomassen is registered as general manager of CETUS EIENDOM AS.

Where is CETUS EIENDOM AS based?

CETUS EIENDOM AS has its business address in Tverrelvdalen.

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.