biztrac. BETA
COMPANY REGISTER PROFILE
915834108 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

J.K. UTVIKLING AS

Org. no. 915834108 Limited company (AS) Hole Incorporated 2015 Active
Revenue 2025 NOK 41.6m
Operating profit NOK 2.3m
Equity NOK −3.0m
Incorporated 2015
Share capital NOK 30,000

Signals

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

J.K. UTVIKLING AS is registered as a limited company in Hole, Buskerud with organisation number 915834108. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive kjøp, salg, drift og utleie av fast eiendom samt alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 41.6m in revenue and NOK 2.3m in operating profit.

Former names: HOLE EIENDOMSUTVIKLING AS

Key figures · 2025

Revenue
NOK 41.6m
▲ +394 %
Operating profit
NOK 2.3m
▲ +384 %
Equity
NOK −3.0m
▼ −2608 %
Est. value
NOK 16.3m

Financial health · 2025

Liquidity
8.79
Very good
Current assets ÷ current liabilities
Profitability
2.3%
Weak
Return on total assets
Solidity
-3.1%
Weak
Equity as a share of total capital

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

Who owns J.K. UTVIKLING AS?

J.K. UTVIKLING AS
NOK 41.6m rev. · NOK 2.3m profit

J.K. UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about J.K. UTVIKLING AS

Who owns J.K. UTVIKLING AS?

J.K. UTLEIE AS is the largest registered owner, with 100.0%.

What is the revenue of J.K. UTVIKLING AS?

J.K. UTVIKLING AS had revenue of NOK 41.6m in 2025.

Where is J.K. UTVIKLING AS based?

J.K. UTVIKLING AS has its business address in Røyse.

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

Report a problem

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