BIZTRAC BETA
Rental and operating of own or leased real estate

KILEN EIENDOM AS

Org. no. 982326184 Limited company (AS) Midt-Telemark Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 323,000
Operating profit NOK 49,000
Equity NOK 575,000
Incorporated 2000
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KILEN EIENDOM AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 982326184. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2000. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, forvaltning, utleie og salg av fast eiendom, samt hva derved står i forbindelse, herunder deltakelse i annen tilsvarende virksomhet ved aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 323,000 in revenue and NOK 49,000 in operating profit.

Key figures · 2024

Revenue
NOK 323,000
Operating profit
NOK 49,000
Equity
NOK 575,000
Est. value
NOK 477,000

Financial health · 2024

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

Who owns KILEN EIENDOM AS?

KRK AS
KILEN EIENDOM AS
NOK 323,000 rev. · NOK 49,000 profit

KILEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KILEN EIENDOM AS

Who owns KILEN EIENDOM AS?

KRK AS is the largest registered owner, with 100.0%.

What is the revenue of KILEN EIENDOM AS?

KILEN EIENDOM AS had revenue of NOK 323,000 in 2024.

Where is KILEN EIENDOM AS based?

KILEN EIENDOM AS has its business address in Bø I Telemark.

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.