BIZTRAC BETA
COMPANY REGISTER PROFILE
933942511 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

LOE KAPITAL AS

Org. no. 933942511 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 18,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

LOE KAPITAL AS is registered as a limited company in Oslo, Oslo with organisation number 933942511. 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: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Operating profit
NOK −6,000
Equity
NOK 18,000
Est. value
NOK 21,000

Financial health · 2024

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

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

Who owns LOE KAPITAL AS?

LARS OMRENG EBERHARD
LOE KAPITAL AS
· NOK −6,000 profit

LOE KAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LOE KAPITAL AS own?

LOE KAPITAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LOE KAPITAL AS

Who owns LOE KAPITAL AS?

LARS OMRENG EBERHARD is the largest registered owner, with 100.0%.

Who is the general manager of LOE KAPITAL AS?

Lars Omreng Eberhard is registered as general manager of LOE KAPITAL AS.

Where is LOE KAPITAL AS based?

LOE KAPITAL 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.