BIZTRAC BETA
Beverage serving activities

LEPHAN INVEST AS

Org. no. 929483561 Limited company (AS) Lillestrøm Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −800
Equity NOK 29,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

LEPHAN INVEST AS is registered as a limited company in Lillestrøm, Akershus with organisation number 929483561. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −800 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −800
Equity
NOK 29,000
Est. value
NOK 39,000

Financial health · 2025

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

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

Who owns LEPHAN INVEST AS?

MAY LEPHAN
LEPHAN INVEST AS
NOK 0 rev. · NOK −800 profit

LEPHAN INVEST AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LEPHAN INVEST AS own?

LEPHAN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LEPHAN INVEST AS

Who owns LEPHAN INVEST AS?

MAY LEPHAN is the largest registered owner, with 40.0%.

What is the revenue of LEPHAN INVEST AS?

LEPHAN INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of LEPHAN INVEST AS?

May Lephan is registered as general manager of LEPHAN INVEST AS.

Where is LEPHAN INVEST AS based?

LEPHAN INVEST AS has its business address in Strømmen.

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.