BIZTRAC BETA
COMPANY REGISTER PROFILE
933207706 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

LGM HOLDING AS

Org. no. 933207706 Limited company (AS) Drammen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 163,000
Operating profit NOK −72,000
Equity NOK 1.1m
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−72k kr).

LGM HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 933207706. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulenttjenester, bedriftsrådgivning og annen administrativ rådgivning, kjøp, salg og utleie av eiendom, kjøp, salg og utleie av bil og motorsykkel, samt investeringer i andre selskaper og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 163,000 in revenue and NOK −72,000 in operating profit.

Key figures · 2025

Revenue
NOK 163,000
Operating profit
NOK −72,000
Equity
NOK 1.1m
Est. value
NOK 666,000

Financial health · 2025

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

Who owns LGM HOLDING AS?

LARS-GUNNAR HUSEBY MARTINSEN
LGM HOLDING AS
NOK 163,000 rev. · NOK −72,000 profit

LGM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LGM HOLDING AS

Who owns LGM HOLDING AS?

LARS-GUNNAR HUSEBY MARTINSEN is the largest registered owner, with 100.0%.

What is the revenue of LGM HOLDING AS?

LGM HOLDING AS had revenue of NOK 163,000 in 2025.

Where is LGM HOLDING AS based?

LGM HOLDING AS has its business address in Drammen.

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.