BIZTRAC BETA
Rental and operating of own or leased real estate

JS2 UTVIKLING AS

Org. no. 924185384 Limited company (AS) Rælingen Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 35.0m
Operating profit NOK 5.4m
Equity NOK −539,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

JS2 UTVIKLING AS is registered as a limited company in Rælingen, Akershus with organisation number 924185384. 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 30,000, divided into 10000 shares. The company's stated purpose is: “Investere i fast eiendom samt all annen virksomhet som står i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 35.0m in revenue and NOK 5.4m in operating profit.

Key figures · 2024

Revenue
NOK 35.0m
Operating profit
NOK 5.4m
Equity
NOK −539,000
Est. value
NOK 59.2m

Financial health · 2024

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

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

Who owns JS2 UTVIKLING AS?

STIMA AS
JS2 UTVIKLING AS
NOK 35.0m rev. · NOK 5.4m profit

JS2 UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

JS2 UTVIKLING AS er morselskap for 3 datterselskaper:

Frequently asked questions about JS2 UTVIKLING AS

Who owns JS2 UTVIKLING AS?

STIMA AS is the largest registered owner, with 100.0%.

What is the revenue of JS2 UTVIKLING AS?

JS2 UTVIKLING AS had revenue of NOK 35.0m in 2024.

Where is JS2 UTVIKLING AS based?

JS2 UTVIKLING AS has its business address in Fjerdingby.

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.