biztrac. BETA
COMPANY REGISTER PROFILE
831170662 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Joinery installation

MBYG CONSTRUCTION AS

Org. no. 831170662 Limited company (AS) Oslo Incorporated 2023 Active
Revenue 2025 NOK 6.7m
Operating profit NOK 138,000
Equity NOK 489,000
Incorporated 2023
Employees 5
Share capital NOK 30,000

MBYG CONSTRUCTION AS is registered as a limited company in Oslo, Oslo with organisation number 831170662. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Oppføring av bygninger, snekkerarbeid og anleggsgartner.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.7m in revenue and NOK 138,000 in operating profit.

Former names: FDV SELSKAPET AS

Key figures · 2025

Revenue
NOK 6.7m
▲ +155 %
Operating profit
NOK 138,000
▼ −71 %
Equity
NOK 489,000
▲ +30 %
Est. value
NOK 858,000

Financial health · 2025

Liquidity
1.20
Satisfactory
Current assets ÷ current liabilities
Profitability
11.6%
Good
Return on total assets
Solidity
41.3%
Very good
Equity as a share of total capital

Who owns MBYG CONSTRUCTION AS?

MBYG CONSTRUCTION AS
NOK 6.7m rev. · NOK 138,000 profit

MBYG CONSTRUCTION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MBYG CONSTRUCTION AS

Who owns MBYG CONSTRUCTION AS?

Mindaugas Baguckas is the largest registered owner, with 100.0%.

What is the revenue of MBYG CONSTRUCTION AS?

MBYG CONSTRUCTION AS had revenue of NOK 6.7m in 2025.

Who is the general manager of MBYG CONSTRUCTION AS?

Mindaugas Baguckas is registered as general manager of MBYG CONSTRUCTION AS.

Where is MBYG CONSTRUCTION AS based?

MBYG CONSTRUCTION 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.