BIZTRAC BETA
Other captive investment companies

AKSJEKLUBBEN FABELAKTIG AS

Org. no. 912592723 Limited company (AS) Drammen Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 220,000
Operating profit NOK 95,000
Equity NOK 2.6m
Incorporated 2013
Share capital NOK 1.8m

AKSJEKLUBBEN FABELAKTIG AS is registered as a limited company in Drammen, Buskerud with organisation number 912592723. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 1.8m, divided into 1800 shares. The company's stated purpose is: “Aksjeklubben Fabelaktig AS har til formål å gi aksjonærene innsikt i og forståelse av verdipapirhandel og næringslivet forøvrig gjennom kjøp og salg av verdipapirer, foredrag, bedriftsbesøk, og jevnlige møter. Formålet er også å skape avkastning for aksjonærene.”. The most recent filed accounts, for the 2025 financial year, show NOK 220,000 in revenue and NOK 95,000 in operating profit.

Key figures · 2025

Revenue
NOK 220,000
Operating profit
NOK 95,000
Equity
NOK 2.6m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns AKSJEKLUBBEN FABELAKTIG AS?

HOLTEFJELL 80 AS
AKSJEKLUBBEN FABELAKTIG AS
NOK 220,000 rev. · NOK 95,000 profit

AKSJEKLUBBEN FABELAKTIG AS has 15 registered shareholders:

All shareholders and roles →

Frequently asked questions about AKSJEKLUBBEN FABELAKTIG AS

Who owns AKSJEKLUBBEN FABELAKTIG AS?

HOLTEFJELL 80 AS is the largest registered owner, with 8.3%.

What is the revenue of AKSJEKLUBBEN FABELAKTIG AS?

AKSJEKLUBBEN FABELAKTIG AS had revenue of NOK 220,000 in 2025.

Where is AKSJEKLUBBEN FABELAKTIG AS based?

AKSJEKLUBBEN FABELAKTIG AS has its business address in Drammen.

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.