BIZTRAC BETA
Other captive investment companies

LØDHORN AS

Org. no. 918123830 Limited company (AS) Flesberg Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 72,000
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).
  • Nylig endring 2026-03-12 Adresseendring registrert 2026-03-12.

LØDHORN AS is registered as a limited company in Flesberg, Buskerud with organisation number 918123830. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie, kjøpe og selge aksjer og andre verdipapirer, samt annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 72,000
Est. value
NOK 66,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 LØDHORN AS?

ANDERS LØDØEN VETHE
LØDHORN AS
NOK 0 rev. · NOK −4,000 profit

LØDHORN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LØDHORN AS own?

LØDHORN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LØDHORN AS

Who owns LØDHORN AS?

ANDERS LØDØEN VETHE is the largest registered owner, with 100.0%.

What is the revenue of LØDHORN AS?

LØDHORN AS had revenue of NOK 0 in 2025.

Where is LØDHORN AS based?

LØDHORN AS has its business address in Lyngdal I Numedal.

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.