biztrac. BETA
COMPANY REGISTER PROFILE
930983780 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

K.I. EIENDOM AS

Org. no. 930983780 Limited company (AS) Fyresdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 202,000
Operating profit NOK 135,000
Equity NOK 564,000
Incorporated 2023
Share capital NOK 30,000

K.I. EIENDOM AS is registered as a limited company in Fyresdal, Telemark with organisation number 930983780. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie, drifte og leie ut fast eiendom og eiendomsutvikling generelt. Selskapet kan eie aksjer/andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 202,000 in revenue and NOK 135,000 in operating profit.

Key figures · 2025

Revenue
NOK 202,000
▲ +9 %
Operating profit
NOK 135,000
▲ +45 %
Equity
NOK 564,000
▲ +24 %
Est. value
NOK 747,000

Financial health · 2025

Liquidity
1.52
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
34.2%
Good
Equity as a share of total capital

Who owns K.I. EIENDOM AS?

K.I. EIENDOM AS
NOK 202,000 rev. · NOK 135,000 profit

K.I. EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about K.I. EIENDOM AS

Who owns K.I. EIENDOM AS?

K. I. INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of K.I. EIENDOM AS?

K.I. EIENDOM AS had revenue of NOK 202,000 in 2025.

Who is the general manager of K.I. EIENDOM AS?

Karl Rune Hansen is registered as general manager of K.I. EIENDOM AS.

Where is K.I. EIENDOM AS based?

K.I. EIENDOM AS has its business address in Fyresdal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.