BIZTRAC BETA
Uoppgitt

KINGO EIENDOM AS

Org. no. 981679237 Limited company (AS) Asker Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6,000
Equity NOK −1.1m
Incorporated 2000
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,1 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

KINGO EIENDOM AS is registered as a limited company in Asker, Akershus with organisation number 981679237. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2000. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Drive kjøp og salg av fast eiendom, samt utvikling av slike. Selskapet kan også delta i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK −1.1m

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

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

Who owns KINGO EIENDOM AS?

ERIK JONSON
KINGO EIENDOM AS
NOK 0 rev. · NOK −6,000 profit

KINGO EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KINGO EIENDOM AS

Who owns KINGO EIENDOM AS?

ERIK JONSON is the largest registered owner, with 50.0%.

What is the revenue of KINGO EIENDOM AS?

KINGO EIENDOM AS had revenue of NOK 0 in 2024.

Who is the general manager of KINGO EIENDOM AS?

Erik Jonson is registered as general manager of KINGO EIENDOM AS.

Where is KINGO EIENDOM AS based?

KINGO EIENDOM AS has its business address in Nesøya.

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.