BIZTRAC BETA
Rental and operating of own or leased real estate

NORDBOTN EIENDOM AS

Org. no. 821017602 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 347,000
Operating profit NOK 217,000
Equity NOK 691,000
Incorporated 2018
Share capital NOK 300,000

NORDBOTN EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 821017602. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 300,000, divided into 300000 shares. The company's stated purpose is: “Investering i, kjøp, utvikling, forvaltning og salg av forretningsvirksomhet, aksjer og andeler, eiendom samt annen aktivitet som står i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 347,000 in revenue and NOK 217,000 in operating profit.

Key figures · 2024

Revenue
NOK 347,000
Operating profit
NOK 217,000
Equity
NOK 691,000
Est. value
NOK 828,000

Financial health · 2024

Liquidity
2.96
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.5%
Good
Equity as a share of total capital

Who owns NORDBOTN EIENDOM AS?

VHF INVEST AS
NORDBOTN EIENDOM AS
NOK 347,000 rev. · NOK 217,000 profit

NORDBOTN EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORDBOTN EIENDOM AS

Who owns NORDBOTN EIENDOM AS?

VHF INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of NORDBOTN EIENDOM AS?

NORDBOTN EIENDOM AS had revenue of NOK 347,000 in 2024.

Who is the general manager of NORDBOTN EIENDOM AS?

Steffen Kirknes is registered as general manager of NORDBOTN EIENDOM AS.

Where is NORDBOTN EIENDOM AS based?

NORDBOTN EIENDOM 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.