BIZTRAC BETA
Rental and operating of own or leased real estate

NATTLANDSLIA 3 AS

Org. no. 830576002 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 533,000
Operating profit NOK 313,000
Equity NOK −291,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−291k kr).

NATTLANDSLIA 3 AS is registered as a limited company in Bergen, Vestland with organisation number 830576002. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 533,000 in revenue and NOK 313,000 in operating profit.

Key figures · 2025

Revenue
NOK 533,000
Operating profit
NOK 313,000
Equity
NOK −291,000
Est. value
NOK 2.1m

Financial health · 2024

Liquidity
3.15
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-3.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NATTLANDSLIA 3 AS?

SIGVE KAHRS HOLDING AS
NATTLANDSLIA 3 AS
NOK 533,000 rev. · NOK 313,000 profit

NATTLANDSLIA 3 AS has 2 registered shareholders:

All shareholders and roles →

Which companies does NATTLANDSLIA 3 AS own?

NATTLANDSLIA 3 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NATTLANDSLIA 3 AS

Who owns NATTLANDSLIA 3 AS?

SIGVE KAHRS HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of NATTLANDSLIA 3 AS?

NATTLANDSLIA 3 AS had revenue of NOK 533,000 in 2025.

Where is NATTLANDSLIA 3 AS based?

NATTLANDSLIA 3 AS has its business address in Bønes.

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.