BIZTRAC BETA
Rental and operating of own or leased real estate

MILLENNIUM COWORK AS

Org. no. 933408213 Limited company (AS) Hareid Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 517,000
Operating profit NOK −79,000
Equity NOK 378,000
Incorporated 2024
Share capital NOK 500,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−79k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MILLENNIUM COWORK AS is registered as a limited company in Hareid, Møre og Romsdal with organisation number 933408213. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Leie og å leie ut lokaler til næringsdrivende.”. The most recent filed accounts, for the 2025 financial year, show NOK 517,000 in revenue and NOK −79,000 in operating profit.

Key figures · 2025

Revenue
NOK 517,000
Operating profit
NOK −79,000
Equity
NOK 378,000
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
1.03
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.8%
Good
Equity as a share of total capital

Who owns MILLENNIUM COWORK AS?

BRAKALI GROUP AS
MILLENNIUM COWORK AS
NOK 517,000 rev. · NOK −79,000 profit

MILLENNIUM COWORK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MILLENNIUM COWORK AS

Who owns MILLENNIUM COWORK AS?

BRAKALI GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of MILLENNIUM COWORK AS?

MILLENNIUM COWORK AS had revenue of NOK 517,000 in 2025.

Where is MILLENNIUM COWORK AS based?

MILLENNIUM COWORK AS has its business address in Hareid.

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.