BIZTRAC BETA
Other real estate activities on a fee or contract basis

KÅSMYRA EIENDOM AS

Org. no. 975356272 Limited company (AS) Drangedal Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK 358,000
Equity NOK 3.1m
Incorporated 1995
Share capital NOK 400,000

Signals

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

KÅSMYRA EIENDOM AS is registered as a limited company in Drangedal, Telemark with organisation number 975356272. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 1995. Registered share capital is NOK 400,000. The company's stated purpose is: “Kjøp, drift og salg av eiendommer og herunder tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK 358,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK 358,000
Equity
NOK 3.1m
Est. value
NOK 2.8m

Financial health · 2025

Liquidity
0.97
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.8%
Good
Equity as a share of total capital

Who owns KÅSMYRA EIENDOM AS?

K. FLOM HOLDING AS
KÅSMYRA EIENDOM AS
NOK 3.6m rev. · NOK 358,000 profit

KÅSMYRA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KÅSMYRA EIENDOM AS

Who owns KÅSMYRA EIENDOM AS?

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

What is the revenue of KÅSMYRA EIENDOM AS?

KÅSMYRA EIENDOM AS had revenue of NOK 3.6m in 2024.

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

Jan Ove Håstul Flom is registered as general manager of KÅSMYRA EIENDOM AS.

Where is KÅSMYRA EIENDOM AS based?

KÅSMYRA EIENDOM AS has its business address in Drangedal.

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.