BIZTRAC BETA
Rental and operating of own or leased real estate

J-K EIENDOM AS

Org. no. 923136819 Limited company (AS) Enebakk Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 943,000
Operating profit NOK 440,000
Equity NOK −93,000
Incorporated 2019
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−93k kr).

J-K EIENDOM AS is registered as a limited company in Enebakk, Akershus with organisation number 923136819. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Utvikling og utleie ut fast eiendom samt de virksomheter som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 943,000 in revenue and NOK 440,000 in operating profit.

Key figures · 2025

Revenue
NOK 943,000
Operating profit
NOK 440,000
Equity
NOK −93,000
Est. value
NOK 1.6m

Financial health · 2025

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

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

Who owns J-K EIENDOM AS?

PETER HØST HANSEN
J-K EIENDOM AS
NOK 943,000 rev. · NOK 440,000 profit

J-K EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about J-K EIENDOM AS

Who owns J-K EIENDOM AS?

PETER HØST HANSEN is the largest registered owner, with 100.0%.

What is the revenue of J-K EIENDOM AS?

J-K EIENDOM AS had revenue of NOK 943,000 in 2025.

Who is the general manager of J-K EIENDOM AS?

Peter Høst Hansen is registered as general manager of J-K EIENDOM AS.

Where is J-K EIENDOM AS based?

J-K EIENDOM AS has its business address in Ytre Enebakk.

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.