biztrac. BETA
COMPANY REGISTER PROFILE
929257731 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

MAK-BUD AS

Org. no. 929257731 Limited company (AS) Trondheim Incorporated 2022 Active
Revenue 2025 NOK 747,000
Operating profit NOK 125,000
Equity NOK 116,000
Incorporated 2022
Share capital NOK 30,000

MAK-BUD AS is registered as a limited company in Trondheim, Trøndelag with organisation number 929257731. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Renovering og oppussing av bygg, flislegging, maletjenester, snekkerarbeid etc. og andre produkter/tjenester som naturlig hører til dette, herunder å delta.”. The most recent filed accounts, for the 2025 financial year, show NOK 747,000 in revenue and NOK 125,000 in operating profit.

Key figures · 2025

Revenue
NOK 747,000
▲ +16 %
Operating profit
NOK 125,000
▲ +201 %
Equity
NOK 116,000
▲ +795 %
Est. value
NOK 244,000

Financial health · 2025

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
54.4%
Very good
Return on total assets
Solidity
44.4%
Very good
Equity as a share of total capital

Who owns MAK-BUD AS?

MAK-BUD AS
NOK 747,000 rev. · NOK 125,000 profit

MAK-BUD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAK-BUD AS

Who owns MAK-BUD AS?

Marek Koronkiewicz is the largest registered owner, with 100.0%.

What is the revenue of MAK-BUD AS?

MAK-BUD AS had revenue of NOK 747,000 in 2025.

Who is the general manager of MAK-BUD AS?

Marek Koronkiewicz is registered as general manager of MAK-BUD AS.

Where is MAK-BUD AS based?

MAK-BUD AS has its business address in Trondheim.

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.