BIZTRAC BETA
Rental and operating of own or leased real estate

VATERLAND AS

Org. no. 996291448 Limited company (AS) Trondheim Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK 162,000
Equity NOK −2.5m
Incorporated 2010
Share capital NOK 116,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,5 mill kr).

VATERLAND AS is registered as a limited company in Trondheim, Trøndelag with organisation number 996291448. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 116,000, divided into 110000 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom samt ved investeringer i andre selskaper innenfor samme bransje.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK 162,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK 162,000
Equity
NOK −2.5m
Est. value
NOK 1.1m

Financial health · 2024

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

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

Who owns VATERLAND AS?

NYLANDER NÆRING AS
VATERLAND AS
NOK 2.4m rev. · NOK 162,000 profit

VATERLAND AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VATERLAND AS own?

VATERLAND AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about VATERLAND AS

Who owns VATERLAND AS?

NYLANDER NÆRING AS is the largest registered owner, with 70.0%.

What is the revenue of VATERLAND AS?

VATERLAND AS had revenue of NOK 2.4m in 2024.

Where is VATERLAND AS based?

VATERLAND AS has its business address in Trondheim.

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.