BIZTRAC BETA
Computing infrastructure, data processing, hosting and related activities

FOLIOSERVER AS

Org. no. 979312741 Limited company (AS) Bærum Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 802,000
Operating profit NOK 177,000
Equity NOK 82.1m
Incorporated 1997
Share capital NOK 3.0m

FOLIOSERVER AS is registered as a limited company in Bærum, Akershus with organisation number 979312741. The business is classified under computing infrastructure, data processing, hosting and related activities (NACE 63.100). The company was incorporated in 1997. Registered share capital is NOK 3.0m, divided into 2995 shares. The company's stated purpose is: “Investering i verdipapirer og fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 802,000 in revenue and NOK 177,000 in operating profit.

Key figures · 2024

Revenue
NOK 802,000
Operating profit
NOK 177,000
Equity
NOK 82.1m
Est. value
NOK 37.8m

Financial health · 2024

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

Who owns FOLIOSERVER AS?

AUGUST GISLERUD ROLFSEN
FOLIOSERVER AS
NOK 802,000 rev. · NOK 177,000 profit

FOLIOSERVER AS has 3 registered shareholders:

All shareholders and roles →

Which companies does FOLIOSERVER AS own?

FOLIOSERVER AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about FOLIOSERVER AS

Who owns FOLIOSERVER AS?

AUGUST GISLERUD ROLFSEN is the largest registered owner, with 98.5%.

What is the revenue of FOLIOSERVER AS?

FOLIOSERVER AS had revenue of NOK 802,000 in 2024.

Who is the general manager of FOLIOSERVER AS?

Dag Øivind Rolfsen is registered as general manager of FOLIOSERVER AS.

Where is FOLIOSERVER AS based?

FOLIOSERVER 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.