BIZTRAC BETA
Construction of residential and non-residential buildings

MELING BYGGTEKNIKK AS

Org. no. 925179701 Limited company (AS) Stavanger Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK 20,000
Equity NOK 363,000
Incorporated 2020
Share capital NOK 30,000

MELING BYGGTEKNIKK AS is registered as a limited company in Stavanger, Rogaland with organisation number 925179701. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Oppføring og rehabilitering av eiendom samt serviceoppdrag innen trevirke og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK 20,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
Operating profit
NOK 20,000
Equity
NOK 363,000
Est. value
NOK 207,000

Financial health · 2025

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

Who owns MELING BYGGTEKNIKK AS?

ADRIAN FOSSE MELING
MELING BYGGTEKNIKK AS
NOK 3.7m rev. · NOK 20,000 profit

MELING BYGGTEKNIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MELING BYGGTEKNIKK AS

Who owns MELING BYGGTEKNIKK AS?

ADRIAN FOSSE MELING is the largest registered owner, with 50.0%.

What is the revenue of MELING BYGGTEKNIKK AS?

MELING BYGGTEKNIKK AS had revenue of NOK 3.7m in 2025.

Who is the general manager of MELING BYGGTEKNIKK AS?

Adrian Fosse Meling is registered as general manager of MELING BYGGTEKNIKK AS.

Where is MELING BYGGTEKNIKK AS based?

MELING BYGGTEKNIKK AS has its business address in Stavanger.

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.