biztrac. BETA
COMPANY REGISTER PROFILE
916269781 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

NEXT STEP EIENDOM AS

Org. no. 916269781 Limited company (AS) Moss Incorporated 2015 Active
Operating profit NOK −561,000
Equity NOK 4.8m
Incorporated 2015
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−561k kr).

NEXT STEP EIENDOM AS is registered as a limited company in Moss, Østfold with organisation number 916269781. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2015. Registered share capital is NOK 1.0m, divided into 1005000 shares. The company's stated purpose is: “selv, gjennom hel eller deleiede selskaper, eller ved samarbeid med andre virksomheter å forstå investeringsvirksomhet, eiendomsforvaltning eller annen virksomhet beslektet med dette.”.

Key figures · 2025

Operating profit
NOK −561,000
▼ −19 %
Equity
NOK 4.8m
▲ +1 %
Est. value
NOK 3.6m

Financial health · 2025

Liquidity
6.98
Very good
Current assets ÷ current liabilities
Profitability
4.9%
Weak
Return on total assets
Solidity
2.6%
Not satisfactory
Equity as a share of total capital

Who owns NEXT STEP EIENDOM AS?

NEXT STEP EIENDOM AS has 8 registered shareholders:

All shareholders and roles →

Which companies does NEXT STEP EIENDOM AS own?

NEXT STEP EIENDOM AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about NEXT STEP EIENDOM AS

Who owns NEXT STEP EIENDOM AS?

HABER NORGE AS is the largest registered owner, with 50.0%.

Who is the general manager of NEXT STEP EIENDOM AS?

Vidar Arild Halvorsen is registered as general manager of NEXT STEP EIENDOM AS.

Where is NEXT STEP EIENDOM AS based?

NEXT STEP EIENDOM AS has its business address in Moss.

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.