BIZTRAC BETA
Uoppgitt

FRIMANN CAPITAL AS

Org. no. 833988492 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 2.4m
Equity NOK 6.0m
Incorporated 2024
Share capital NOK 30,000

FRIMANN CAPITAL AS is registered as a limited company in Bærum, Akershus with organisation number 833988492. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Investering i aksjer, andre verdipapirer, andre eiendeler og fast eiendom samt yte konsulenttjenester og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 2.4m in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK 2.4m
Equity
NOK 6.0m
Est. value
NOK 10.7m

Financial health · 2025

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

Who owns FRIMANN CAPITAL AS?

GLENN-ARILD SKOGVOLL VEIBY
FRIMANN CAPITAL AS
NOK 2.5m rev. · NOK 2.4m profit

FRIMANN CAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FRIMANN CAPITAL AS own?

FRIMANN CAPITAL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FRIMANN CAPITAL AS

Who owns FRIMANN CAPITAL AS?

GLENN-ARILD SKOGVOLL VEIBY is the largest registered owner, with 100.0%.

What is the revenue of FRIMANN CAPITAL AS?

FRIMANN CAPITAL AS had revenue of NOK 2.5m in 2025.

Who is the general manager of FRIMANN CAPITAL AS?

Glenn-Arild Skogvoll Veiby is registered as general manager of FRIMANN CAPITAL AS.

Where is FRIMANN CAPITAL AS based?

FRIMANN CAPITAL AS has its business address in Stabekk.

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.