BIZTRAC BETA
Construction of residential and non-residential buildings

MULTI BYGG PARTNER AS

Org. no. 918588930 Limited company (AS) Lier Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 4.1m
Operating profit NOK 366,000
Equity NOK 160,000
Incorporated 2017
Share capital NOK 30,000

MULTI BYGG PARTNER AS is registered as a limited company in Lier, Buskerud with organisation number 918588930. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapets formål er alt innen bygg: Nybygg, rehabilitering, vedlikehold og drift, samt konsulent- og takseringstjenester, prosjektering og byggeledelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.1m in revenue and NOK 366,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.1m
Operating profit
NOK 366,000
Equity
NOK 160,000
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.3%
Good
Equity as a share of total capital

Who owns MULTI BYGG PARTNER AS?

MERSUDIN VISNJIC
MULTI BYGG PARTNER AS
NOK 4.1m rev. · NOK 366,000 profit

MULTI BYGG PARTNER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MULTI BYGG PARTNER AS

Who owns MULTI BYGG PARTNER AS?

MERSUDIN VISNJIC is the largest registered owner, with 80.0%.

What is the revenue of MULTI BYGG PARTNER AS?

MULTI BYGG PARTNER AS had revenue of NOK 4.1m in 2025.

Who is the general manager of MULTI BYGG PARTNER AS?

Geir Solberg is registered as general manager of MULTI BYGG PARTNER AS.

Where is MULTI BYGG PARTNER AS based?

MULTI BYGG PARTNER AS has its business address in Lierstranda.

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.