BIZTRAC BETA
Rental and operating of own or leased real estate

KÅGTIND EIENDOM AS

Org. no. 921201362 Limited company (AS) Nordreisa Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 268,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

KÅGTIND EIENDOM AS is registered as a limited company in Nordreisa, Troms with organisation number 921201362. 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 30 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, selskapet kan ved aksjetegning eller på annen måte eie andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 268,000
Est. value
NOK 245,000

Financial health · 2025

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

Who owns KÅGTIND EIENDOM AS?

NILOY HOLDING AS
KÅGTIND EIENDOM AS
NOK 0 rev. · NOK −14,000 profit

KÅGTIND EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KÅGTIND EIENDOM AS

Who owns KÅGTIND EIENDOM AS?

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

What is the revenue of KÅGTIND EIENDOM AS?

KÅGTIND EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of KÅGTIND EIENDOM AS?

Øyvind Nilsen is registered as general manager of KÅGTIND EIENDOM AS.

Where is KÅGTIND EIENDOM AS based?

KÅGTIND EIENDOM AS has its business address in Storslett.

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.