BIZTRAC BETA
COMPANY REGISTER PROFILE
930212970 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

STORESKJERET AS

Org. no. 930212970 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 930,000
Incorporated 2022
Share capital NOK 150,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).
  • Nylig endring 2026-08-06 Aksjekapital registrert 2026-08-06.

STORESKJERET AS is registered as a limited company in Trondheim, Trøndelag with organisation number 930212970. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 150,000, divided into 50000 shares. The company's stated purpose is: “Investering i aksjer, eiendom og andre verdipapirer, samt konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 930,000
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
941.23
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
99.9%
Very good
Equity as a share of total capital

Who owns STORESKJERET AS?

STORESKJERET AS
NOK 0 rev. · NOK −5,000 profit

STORESKJERET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORESKJERET AS

Who owns STORESKJERET AS?

HELGE KVALVIK is the largest registered owner, with 100.0%.

What is the revenue of STORESKJERET AS?

STORESKJERET AS had revenue of NOK 0 in 2025.

Who is the general manager of STORESKJERET AS?

Helge Kvalvik is registered as general manager of STORESKJERET AS.

Where is STORESKJERET AS based?

STORESKJERET AS has its business address in Trondheim.

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

Report a problem

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