BIZTRAC BETA
COMPANY REGISTER PROFILE
989480405 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

KROGRUD HOLDING AS

Org. no. 989480405 Limited company (AS) Ringsaker Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 926,000
Incorporated 2006
Share capital NOK 100,000

Signals

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

KROGRUD HOLDING AS is registered as a limited company in Ringsaker, Innlandet with organisation number 989480405. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å investere i andre selskaper samt hva som herved står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −12,000
Equity
NOK 926,000
Est. value
NOK 706,000

Financial health · 2025

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

Who owns KROGRUD HOLDING AS?

KROGRUD HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about KROGRUD HOLDING AS

Who owns KROGRUD HOLDING AS?

GEIR KROGRUD is the largest registered owner, with 30.0%.

Where is KROGRUD HOLDING AS based?

KROGRUD HOLDING AS has its business address in Stavsjø.

Property

Business address Mengsholvegen 412, 2353 Stavsjø
Cadastral unit 3411-661/15/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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