biztrac. BETA
COMPANY REGISTER PROFILE
931736922 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

NEDRE LIENVEGEN 14 AS

Org. no. 931736922 Limited company (AS) Hol Incorporated 2023 Active
Revenue 2025 NOK 566,000
Operating profit NOK 445,000
Equity NOK 154,000
Incorporated 2023
Share capital NOK 30,000

NEDRE LIENVEGEN 14 AS is registered as a limited company in Hol, Buskerud with organisation number 931736922. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie, drive og leie ut forretningseiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 566,000 in revenue and NOK 445,000 in operating profit.

Key figures · 2025

Revenue
NOK 566,000
▲ +12 %
Operating profit
NOK 445,000
▲ +21 %
Equity
NOK 154,000
▲ +0 %
Est. value
NOK 833,000

Financial health · 2025

Liquidity
0.13
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
2.5%
Not satisfactory
Equity as a share of total capital

Who owns NEDRE LIENVEGEN 14 AS?

NEDRE LIENVEGEN 14 AS
NOK 566,000 rev. · NOK 445,000 profit

NEDRE LIENVEGEN 14 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NEDRE LIENVEGEN 14 AS

Who owns NEDRE LIENVEGEN 14 AS?

Martin Haaland is the largest registered owner, with 99.0%.

What is the revenue of NEDRE LIENVEGEN 14 AS?

NEDRE LIENVEGEN 14 AS had revenue of NOK 566,000 in 2025.

Who is the general manager of NEDRE LIENVEGEN 14 AS?

Martin Haaland is registered as general manager of NEDRE LIENVEGEN 14 AS.

Where is NEDRE LIENVEGEN 14 AS based?

NEDRE LIENVEGEN 14 AS has its business address in Geilo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.