BIZTRAC BETA
COMPANY REGISTER PROFILE
987701471 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

KOS EIENDOM AS

Org. no. 987701471 Limited company (AS) Askøy Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 358,000
Operating profit NOK −25,000
Equity NOK 81,000
Incorporated 2004
Share capital NOK 150,000

Signals

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

KOS EIENDOM AS is registered as a limited company in Askøy, Vestland with organisation number 987701471. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2004. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Kjøp og salg av eiendom, herunder leie- og utleie virksomhet, samt det som naturlig står i denne forbindelse, samt deltakelse i andre selskaper og virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 358,000 in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 358,000
▲ +191 %
Operating profit
NOK −25,000
▼ −563 %
Equity
NOK 81,000
▼ −46 %
Est. value
NOK 317,000

Financial health · 2025

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
-1.1%
Not satisfactory
Return on total assets
Solidity
3.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KOS EIENDOM AS?

KOS EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about KOS EIENDOM AS

Who owns KOS EIENDOM AS?

EINAR TORSVIK is the largest registered owner, with 33.3%.

What is the revenue of KOS EIENDOM AS?

KOS EIENDOM AS had revenue of NOK 358,000 in 2025.

Where is KOS EIENDOM AS based?

KOS EIENDOM AS has its business address in Hauglandshella.

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

Report a problem

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