BIZTRAC BETA
Rental and operating of own or leased real estate

BARDUFOSS HOTELL EIENDOM AS

Org. no. 921734786 Limited company (AS) Målselv Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 6.2m
Operating profit NOK 3.1m
Equity NOK 648,000
Incorporated 2018
Share capital NOK 30,000

BARDUFOSS HOTELL EIENDOM AS is registered as a limited company in Målselv, Troms with organisation number 921734786. 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 30,000, divided into 10000 shares. The company's stated purpose is: “Investere og eie andre selskaper samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.2m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 6.2m
Operating profit
NOK 3.1m
Equity
NOK 648,000
Est. value
NOK 4.8m

Financial health · 2024

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

Who owns BARDUFOSS HOTELL EIENDOM AS?

KTN HOLDING AS
BARDUFOSS HOTELL EIENDOM AS
NOK 6.2m rev. · NOK 3.1m profit

BARDUFOSS HOTELL EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BARDUFOSS HOTELL EIENDOM AS

Who owns BARDUFOSS HOTELL EIENDOM AS?

KTN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BARDUFOSS HOTELL EIENDOM AS?

BARDUFOSS HOTELL EIENDOM AS had revenue of NOK 6.2m in 2024.

Who is the general manager of BARDUFOSS HOTELL EIENDOM AS?

Kristin Nymo is registered as general manager of BARDUFOSS HOTELL EIENDOM AS.

Where is BARDUFOSS HOTELL EIENDOM AS based?

BARDUFOSS HOTELL EIENDOM AS has its business address in Bardufoss.

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.