BIZTRAC BETA
Civil engineering activities

MELING BYGG AS

Org. no. 936621716 Limited company (AS) Lyngdal Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 99,000
Operating profit NOK 19,000
Equity NOK 38,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-10-29.

MELING BYGG AS is registered as a limited company in Lyngdal, Agder with organisation number 936621716. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg av prosjekt og byggtekniske tjenester. Tømring, oppføring av bygg, oppussing og andre produkter og tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 99,000 in revenue and NOK 19,000 in operating profit.

Key figures · 2025

Revenue
NOK 99,000
Operating profit
NOK 19,000
Equity
NOK 38,000
Est. value
NOK 100,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MELING BYGG AS?

EKOS HOLDING AS
MELING BYGG AS
NOK 99,000 rev. · NOK 19,000 profit

MELING BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MELING BYGG AS

Who owns MELING BYGG AS?

EKOS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MELING BYGG AS?

MELING BYGG AS had revenue of NOK 99,000 in 2025.

Who is the general manager of MELING BYGG AS?

Andreas Espeland Meling is registered as general manager of MELING BYGG AS.

Where is MELING BYGG AS based?

MELING BYGG AS has its business address in Lyngdal.

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.