BIZTRAC BETA
Rental and operating of own or leased real estate

LAUVTJERNVEIEN 4 AS

Org. no. 927245973 Limited company (AS) Øvre Eiker Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 669,000
Equity NOK 11.6m
Incorporated 2021
Share capital NOK 200,000

Signals

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

LAUVTJERNVEIEN 4 AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 927245973. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 200,000, divided into 1000 shares. The company's stated purpose is: “Være et holdingselskap for å eie, drive, leie ut og utvikle fast eiendom, samt hva som herved står i forbindelse, herunder delta i annen virksomhet beslektet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 669,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 669,000
Equity
NOK 11.6m
Est. value
NOK 9.4m

Financial health · 2025

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

Who owns LAUVTJERNVEIEN 4 AS?

FROGNES AS
LAUVTJERNVEIEN 4 AS
NOK 1.1m rev. · NOK 669,000 profit

LAUVTJERNVEIEN 4 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAUVTJERNVEIEN 4 AS

Who owns LAUVTJERNVEIEN 4 AS?

FROGNES AS is the largest registered owner, with 100.0%.

What is the revenue of LAUVTJERNVEIEN 4 AS?

LAUVTJERNVEIEN 4 AS had revenue of NOK 1.1m in 2025.

Where is LAUVTJERNVEIEN 4 AS based?

LAUVTJERNVEIEN 4 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.