BIZTRAC BETA
Rental and operating of own or leased real estate

JIKS EIENDOM AS

Org. no. 985485100 Limited company (AS) Modum Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 539,000
Operating profit NOK 351,000
Equity NOK −1.1m
Incorporated 2003
Share capital NOK 102,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,1 mill kr).

JIKS EIENDOM AS is registered as a limited company in Modum, Buskerud with organisation number 985485100. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 102,000, divided into 102 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom samt dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 539,000 in revenue and NOK 351,000 in operating profit.

Key figures · 2024

Revenue
NOK 539,000
Operating profit
NOK 351,000
Equity
NOK −1.1m
Est. value
NOK 1.8m

Financial health · 2024

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

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

Who owns JIKS EIENDOM AS?

INGER HELLUM
JIKS EIENDOM AS
NOK 539,000 rev. · NOK 351,000 profit

JIKS EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about JIKS EIENDOM AS

Who owns JIKS EIENDOM AS?

INGER HELLUM is the largest registered owner, with 33.3%.

What is the revenue of JIKS EIENDOM AS?

JIKS EIENDOM AS had revenue of NOK 539,000 in 2024.

Who is the general manager of JIKS EIENDOM AS?

Inger Hellum is registered as general manager of JIKS EIENDOM AS.

Where is JIKS EIENDOM AS based?

JIKS EIENDOM AS has its business address in Vikersund.

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.