BIZTRAC BETA
Civil engineering activities

LJG MOLDE AS

Org. no. 918547681 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 195,000
Operating profit NOK 155,000
Equity NOK −311,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−311k kr).

LJG MOLDE AS is registered as a limited company in Oslo, Oslo with organisation number 918547681. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulenttjenester innen mur-, puss-, fasade-, flis- og natursteinarbeider, herunder byggeledelse og kontroll, samt alt som dertil hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 195,000 in revenue and NOK 155,000 in operating profit.

Key figures · 2024

Revenue
NOK 195,000
Operating profit
NOK 155,000
Equity
NOK −311,000
Est. value
NOK 961,000

Financial health · 2024

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

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

Who owns LJG MOLDE AS?

PER EGIL NYGÅRD
LJG MOLDE AS
NOK 195,000 rev. · NOK 155,000 profit

LJG MOLDE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LJG MOLDE AS

Who owns LJG MOLDE AS?

PER EGIL NYGÅRD is the largest registered owner, with 100.0%.

What is the revenue of LJG MOLDE AS?

LJG MOLDE AS had revenue of NOK 195,000 in 2024.

Who is the general manager of LJG MOLDE AS?

Per Egil Nygård is registered as general manager of LJG MOLDE AS.

Where is LJG MOLDE AS based?

LJG MOLDE 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 15.06.2026.

Report a problem

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