biztrac. BETA
COMPANY REGISTER PROFILE
935320259 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Accounting and bookkeeping

KOLGROV HOLDING AS

Org. no. 935320259 Limited company (AS) Elverum Incorporated 2025 Active
Operating profit NOK −5,000
Equity NOK 56,000
Incorporated 2025
Share capital NOK 40,000

Signals

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

KOLGROV HOLDING AS is registered as a limited company in Elverum, Innlandet with organisation number 935320259. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2025. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Eierskap i andre bedrifter uansett bransje og andre produkter/tjenester som naturlig hører sammen med dette herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Investeringer og kapitalplasseringer.”.

Key figures · 2025

Operating profit
NOK −5,000
Equity
NOK 56,000
Est. value
NOK 249,000

Financial health · 2025

Liquidity
10.00
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
95.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KOLGROV HOLDING AS?

KOLGROV HOLDING AS
· NOK −5,000 profit

KOLGROV HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KOLGROV HOLDING AS own?

KOLGROV HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KOLGROV HOLDING AS

Who owns KOLGROV HOLDING AS?

Øyvind Kolgrov is the largest registered owner, with 100.0%.

Where is KOLGROV HOLDING AS based?

KOLGROV HOLDING AS has its business address in Elverum.

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.