BIZTRAC BETA
Development of building projects

JN UTVIKLING AS

Org. no. 919579366 Limited company (AS) Ullensaker Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 199,000
Operating profit NOK −52,000
Equity NOK −1.5m
Incorporated 2017
Share capital NOK 30,000

Signals

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

JN UTVIKLING AS is registered as a limited company in Ullensaker, Akershus with organisation number 919579366. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg og utvikling av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 199,000 in revenue and NOK −52,000 in operating profit.

Key figures · 2025

Revenue
NOK 199,000
Operating profit
NOK −52,000
Equity
NOK −1.5m

Financial health · 2024

Liquidity
2.66
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-22.0%
Weak
Equity as a share of total capital

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

Who owns JN UTVIKLING AS?

HANS JØRGEN BORGEN
JN UTVIKLING AS
NOK 199,000 rev. · NOK −52,000 profit

JN UTVIKLING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does JN UTVIKLING AS own?

JN UTVIKLING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JN UTVIKLING AS

Who owns JN UTVIKLING AS?

HANS JØRGEN BORGEN is the largest registered owner, with 93.3%.

What is the revenue of JN UTVIKLING AS?

JN UTVIKLING AS had revenue of NOK 199,000 in 2025.

Where is JN UTVIKLING AS based?

JN UTVIKLING AS has its business address in Nordkisa.

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.