biztrac. BETA
COMPANY REGISTER PROFILE
916999615 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
In liquidation UPDATED 03.10.2026
⚠SJENSTADBERGET AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Development of building projects

SJENSTADBERGET AS

Org. no. 916999615 Limited company (AS) Ålesund Incorporated 2016 In liquidation
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 387,000
Equity NOK 1.1m
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

SJENSTADBERGET AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 916999615. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investere i fritidseiendommer, verdipapirer, fast eiendom og det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 387,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 387,000
▲ +1 %
Equity
NOK 1.1m
▲ +65 %

Financial health · 2025

Liquidity
13.06
Very good
Current assets ÷ current liabilities
Profitability
36.2%
Very good
Return on total assets
Solidity
92.3%
Very good
Equity as a share of total capital

Who owns SJENSTADBERGET AS?

SJENSTADBERGET AS
NOK 0 rev. · NOK 387,000 profit

SJENSTADBERGET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SJENSTADBERGET AS

Who owns SJENSTADBERGET AS?

VESA INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of SJENSTADBERGET AS?

SJENSTADBERGET AS had revenue of NOK 0 in 2025.

Where is SJENSTADBERGET AS based?

SJENSTADBERGET AS has its business address in Ålesund.

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.