BIZTRAC BETA
COMPANY REGISTER PROFILE
892075352 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

SPAREGRIS AS

Org. no. 892075352 Limited company (AS) Bærum Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 288,000
Incorporated 2007
Share capital NOK 100,000

Signals

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

SPAREGRIS AS is registered as a limited company in Bærum, Akershus with organisation number 892075352. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i selskaper/aksjer.”. 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 288,000
Est. value
NOK 263,000

Financial health · 2025

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

Who owns SPAREGRIS AS?

DAG HELLERUD
SPAREGRIS AS
NOK 0 rev. · NOK −5,000 profit

SPAREGRIS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SPAREGRIS AS own?

SPAREGRIS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SPAREGRIS AS

Who owns SPAREGRIS AS?

DAG HELLERUD is the largest registered owner, with 100.0%.

What is the revenue of SPAREGRIS AS?

SPAREGRIS AS had revenue of NOK 0 in 2025.

Who is the general manager of SPAREGRIS AS?

Dag Hellerud is registered as general manager of SPAREGRIS AS.

Where is SPAREGRIS AS based?

SPAREGRIS AS has its business address in Jar.

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.