BIZTRAC BETA
Rental and operating of own or leased real estate

YTONGVEIEN 18 AS

Org. no. 924011114 Limited company (AS) Øvre Eiker Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 733,000
Operating profit NOK 12,000
Equity NOK 104,000
Incorporated 2019
Share capital NOK 200,000

YTONGVEIEN 18 AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 924011114. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 200,000, divided into 200000 shares. The company's stated purpose is: “Selskapets virksomhet skal være anskaffelse, utvikling, utleie og salg av fast eiendom samt ved kjøp av aksjer eller på annen måte delta i andre virksomheter av enhver art”. The most recent filed accounts, for the 2025 financial year, show NOK 733,000 in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 733,000
Operating profit
NOK 12,000
Equity
NOK 104,000
Est. value
NOK 104,000

Financial health · 2025

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

Who owns YTONGVEIEN 18 AS?

ØIVIND BRÅTHEN HOLDING AS
YTONGVEIEN 18 AS
NOK 733,000 rev. · NOK 12,000 profit

YTONGVEIEN 18 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about YTONGVEIEN 18 AS

Who owns YTONGVEIEN 18 AS?

ØIVIND BRÅTHEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of YTONGVEIEN 18 AS?

YTONGVEIEN 18 AS had revenue of NOK 733,000 in 2025.

Who is the general manager of YTONGVEIEN 18 AS?

Øivind Bråthen is registered as general manager of YTONGVEIEN 18 AS.

Where is YTONGVEIEN 18 AS based?

YTONGVEIEN 18 AS has its business address in Hokksund.

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.