BIZTRAC BETA
Joinery installation

MODULVEGGER OSLO AS

Org. no. 930114065 Limited company (AS) Oslo Incorporated 1967 Active
Ownership graph ↗
Revenue 2024 NOK 378.5m
Operating profit NOK 19.0m
Equity NOK 15.7m
Incorporated 1967
Employees 114
Share capital NOK 1.8m

MODULVEGGER OSLO AS is registered as a limited company in Oslo, Oslo with organisation number 930114065. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 1967 and has 114 registered employees. Registered share capital is NOK 1.8m, divided into 18261 shares. The company's stated purpose is: “Kjøp, salg, agenturvirksomhet samt deltagelse i andre selskaper. Hertil kommer garantistillelse og ervervelse av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 378.5m in revenue and NOK 19.0m in operating profit.

Key figures · 2024

Revenue
NOK 378.5m
Operating profit
NOK 19.0m
Equity
NOK 15.7m
Est. value
NOK 69.9m

Financial health · 2024

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

Who owns MODULVEGGER OSLO AS?

MODULVEGGER AS
MODULVEGGER OSLO AS
NOK 378.5m rev. · NOK 19.0m profit

MODULVEGGER OSLO AS has 4 registered shareholders:

All shareholders and roles →

Group structure

MODULVEGGER OSLO AS er morselskap for 5 datterselskaper:

Frequently asked questions about MODULVEGGER OSLO AS

Who owns MODULVEGGER OSLO AS?

MODULVEGGER AS is the largest registered owner, with 71.3%.

What is the revenue of MODULVEGGER OSLO AS?

MODULVEGGER OSLO AS had revenue of NOK 378.5m in 2024.

Who is the general manager of MODULVEGGER OSLO AS?

Ole André Garnvik is registered as general manager of MODULVEGGER OSLO AS.

Where is MODULVEGGER OSLO AS based?

MODULVEGGER OSLO AS has its business address in Oslo.

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.