BIZTRAC BETA
Other captive investment companies

GYGREKJEFTEN AS

Org. no. 915038212 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −15,000
Equity NOK 275,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

GYGREKJEFTEN AS is registered as a limited company in Oslo, Oslo with organisation number 915038212. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å investere i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK 275,000
Est. value
NOK 251,000

Financial health · 2025

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

Who owns GYGREKJEFTEN AS?

PER ASBJØRN RISNES
GYGREKJEFTEN AS
NOK 0 rev. · NOK −15,000 profit

GYGREKJEFTEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GYGREKJEFTEN AS own?

GYGREKJEFTEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GYGREKJEFTEN AS

Who owns GYGREKJEFTEN AS?

PER ASBJØRN RISNES is the largest registered owner, with 100.0%.

What is the revenue of GYGREKJEFTEN AS?

GYGREKJEFTEN AS had revenue of NOK 0 in 2025.

Who is the general manager of GYGREKJEFTEN AS?

Per Asbjørn Risnes is registered as general manager of GYGREKJEFTEN AS.

Where is GYGREKJEFTEN AS based?

GYGREKJEFTEN AS has its business address in Oslo.

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.