BIZTRAC BETA
Buying and selling of own real estate

BRUVEIEN UTVIKLING AS

Org. no. 923809023 Limited company (AS) Lier Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 295,000
Operating profit NOK 232,000
Equity NOK 13.1m
Incorporated 2019
Share capital NOK 40,000

Signals

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

BRUVEIEN UTVIKLING AS is registered as a limited company in Lier, Buskerud with organisation number 923809023. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 40,000, divided into 1000 shares. The company's stated purpose is: “Næringsvirksomhet ved erverv og drift og salg av fast eiendom, deltagelse i andre foretak og det som naturlig står i forbindelse hermed. Samt investeringer og aksjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 295,000 in revenue and NOK 232,000 in operating profit.

Key figures · 2024

Revenue
NOK 295,000
Operating profit
NOK 232,000
Equity
NOK 13.1m
Est. value
NOK 9.4m

Financial health · 2024

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

Who owns BRUVEIEN UTVIKLING AS?

GIGANT GRUPPEN AS
BRUVEIEN UTVIKLING AS
NOK 295,000 rev. · NOK 232,000 profit

BRUVEIEN UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRUVEIEN UTVIKLING AS

Who owns BRUVEIEN UTVIKLING AS?

GIGANT GRUPPEN AS is the largest registered owner, with 90.1%.

What is the revenue of BRUVEIEN UTVIKLING AS?

BRUVEIEN UTVIKLING AS had revenue of NOK 295,000 in 2024.

Where is BRUVEIEN UTVIKLING AS based?

BRUVEIEN UTVIKLING AS has its business address in Lier.

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.