BIZTRAC BETA
Construction of residential and non-residential buildings

MAGIBYGG AS

Org. no. 991189173 Limited company (AS) Tønsberg Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK 544,000
Equity NOK 820,000
Incorporated 2007
Employees 6
Share capital NOK 100,000

MAGIBYGG AS is registered as a limited company in Tønsberg, Vestfold with organisation number 991189173. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2007 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Bygg, sandblåsing, stillasarbeid, rehabilitering av mur og betong, mekanisk produksjon og andre produkter/tjenester som naturlig hører sammen med dette, herunder delta i selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.3m in revenue and NOK 544,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK 544,000
Equity
NOK 820,000
Est. value
NOK 2.0m

Financial health · 2024

Liquidity
1.85
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
43.8%
Very good
Equity as a share of total capital

Who owns MAGIBYGG AS?

VIDAR THETING JENSEN
MAGIBYGG AS
NOK 5.3m rev. · NOK 544,000 profit

MAGIBYGG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MAGIBYGG AS

Who owns MAGIBYGG AS?

VIDAR THETING JENSEN is the largest registered owner, with 60.0%.

What is the revenue of MAGIBYGG AS?

MAGIBYGG AS had revenue of NOK 5.3m in 2024.

Who is the general manager of MAGIBYGG AS?

Marijus Leliukas is registered as general manager of MAGIBYGG AS.

Where is MAGIBYGG AS based?

MAGIBYGG AS has its business address in Barkåker.

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.