BIZTRAC BETA
Other manufacturing n.e.c.

LEHMKUHL AS

Org. no. 980112799 Limited company (AS) Lier Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK −3.6m
Equity NOK −3.8m
Incorporated 1998
Share capital NOK 500,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,8 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3,6 mill kr).

LEHMKUHL AS is registered as a limited company in Lier, Buskerud with organisation number 980112799. The business is classified under other manufacturing n.e.c. (NACE 32.990). The company was incorporated in 1998. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Produksjon, salg og investeringer, og all annen forretningsvirksomhet i den forbindelse, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK −3.6m in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK −3.6m
Equity
NOK −3.8m

Financial health · 2024

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-188.8%
Weak
Equity as a share of total capital

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

Who owns LEHMKUHL AS?

DIDRIK JOAKIM LEHMKUHL
LEHMKUHL AS
NOK 1.5m rev. · NOK −3.6m profit

LEHMKUHL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEHMKUHL AS

Who owns LEHMKUHL AS?

DIDRIK JOAKIM LEHMKUHL is the largest registered owner, with 100.0%.

What is the revenue of LEHMKUHL AS?

LEHMKUHL AS had revenue of NOK 1.5m in 2024.

Who is the general manager of LEHMKUHL AS?

Didrik Joakim Lehmkuhl is registered as general manager of LEHMKUHL AS.

Where is LEHMKUHL AS based?

LEHMKUHL AS has its business address in Lier.

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.