BIZTRAC BETA
Office administrative and support activities

STORBILVASKEN NORGE AS

Org. no. 925529109 Limited company (AS) Hamar Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 64.5m
Operating profit NOK 1.8m
Equity NOK 2.4m
Incorporated 2020
Share capital NOK 1.5m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STORBILVASKEN NORGE AS is registered as a limited company in Hamar, Innlandet with organisation number 925529109. The business is classified under office administrative and support activities (NACE 82.100). The company was incorporated in 2020. Registered share capital is NOK 1.5m, divided into 150 shares. The company's stated purpose is: “Hovedkontortjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 64.5m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 64.5m
Operating profit
NOK 1.8m
Equity
NOK 2.4m
Est. value
NOK 8.6m

Financial health · 2025

Liquidity
1.30
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.4%
Satisfactory
Equity as a share of total capital

Who owns STORBILVASKEN NORGE AS?

FLOCKS HOLDING AS
STORBILVASKEN NORGE AS
NOK 64.5m rev. · NOK 1.8m profit

STORBILVASKEN NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORBILVASKEN NORGE AS

Who owns STORBILVASKEN NORGE AS?

FLOCKS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of STORBILVASKEN NORGE AS?

STORBILVASKEN NORGE AS had revenue of NOK 64.5m in 2025.

Who is the general manager of STORBILVASKEN NORGE AS?

Lars Ole Storihle is registered as general manager of STORBILVASKEN NORGE AS.

Where is STORBILVASKEN NORGE AS based?

STORBILVASKEN NORGE AS has its business address in Ingeberg.

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.