BIZTRAC BETA
Rental and operating of own or leased real estate

SERVATUR HOLDING AS

Org. no. 991710485 Limited company (AS) Gjøvik Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 2.0m
Incorporated 2007
Share capital NOK 42.9m

SERVATUR HOLDING AS is registered as a limited company in Gjøvik, Innlandet with organisation number 991710485. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 42.9m, divided into 6134850 shares. The company's stated purpose is: “Erverve, forvalte og selge aksjer, andeler og faste eiendommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 2.0m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns SERVATUR HOLDING AS?

FREDENSBORG HORECA AS
SERVATUR HOLDING AS
NOK 0 rev. · NOK 0 profit

SERVATUR HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SERVATUR HOLDING AS own?

SERVATUR HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SERVATUR HOLDING AS

Who owns SERVATUR HOLDING AS?

FREDENSBORG HORECA AS is the largest registered owner, with 48.9%.

What is the revenue of SERVATUR HOLDING AS?

SERVATUR HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of SERVATUR HOLDING AS?

Kai-Robert Mikaelsen is registered as general manager of SERVATUR HOLDING AS.

Where is SERVATUR HOLDING AS based?

SERVATUR HOLDING AS has its business address in Gjøvik.

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.