BIZTRAC BETA
Construction of residential and non-residential buildings

RØVIK MULTISERVICE AS

Org. no. 921715595 Limited company (AS) Stjørdal Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 8.1m
Operating profit NOK 432,000
Equity NOK 487,000
Incorporated 2018
Employees 9
Share capital NOK 30,000

RØVIK MULTISERVICE AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 921715595. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 6 shares. The company's stated purpose is: “Bygg og anleggsarbeid og annet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.1m in revenue and NOK 432,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.1m
Operating profit
NOK 432,000
Equity
NOK 487,000
Est. value
NOK 1.6m

Financial health · 2024

Liquidity
1.11
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.3%
Good
Equity as a share of total capital

Who owns RØVIK MULTISERVICE AS?

JOHAN SIGURD BUAN RØVIK
RØVIK MULTISERVICE AS
NOK 8.1m rev. · NOK 432,000 profit

RØVIK MULTISERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RØVIK MULTISERVICE AS

Who owns RØVIK MULTISERVICE AS?

JOHAN SIGURD BUAN RØVIK is the largest registered owner, with 100.0%.

What is the revenue of RØVIK MULTISERVICE AS?

RØVIK MULTISERVICE AS had revenue of NOK 8.1m in 2024.

Who is the general manager of RØVIK MULTISERVICE AS?

Johan Sigurd Buan Røvik is registered as general manager of RØVIK MULTISERVICE AS.

Where is RØVIK MULTISERVICE AS based?

RØVIK MULTISERVICE AS has its business address in Hegra.

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.