BIZTRAC BETA
Business and other management consultancy activities

STORRGROVIN AS

Org. no. 825360042 Limited company (AS) Lunner Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 474,000
Operating profit NOK 390,000
Equity NOK 135,000
Incorporated 2020
Share capital NOK 30,000

STORRGROVIN AS is registered as a limited company in Lunner, Akershus with organisation number 825360042. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rådgivnings- og konsulent-tjenester, herunder deltakelse i styrer o.l. Kjøp og salg av verdipapirer, fast eiendom o.l.”. The most recent filed accounts, for the 2025 financial year, show NOK 474,000 in revenue and NOK 390,000 in operating profit.

Key figures · 2025

Revenue
NOK 474,000
Operating profit
NOK 390,000
Equity
NOK 135,000
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns STORRGROVIN AS?

KNUT HOVIND
STORRGROVIN AS
NOK 474,000 rev. · NOK 390,000 profit

STORRGROVIN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STORRGROVIN AS own?

STORRGROVIN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STORRGROVIN AS

Who owns STORRGROVIN AS?

KNUT HOVIND is the largest registered owner, with 100.0%.

What is the revenue of STORRGROVIN AS?

STORRGROVIN AS had revenue of NOK 474,000 in 2025.

Who is the general manager of STORRGROVIN AS?

Knut Hovind is registered as general manager of STORRGROVIN AS.

Where is STORRGROVIN AS based?

STORRGROVIN AS has its business address in Harestua.

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.