biztrac. BETA
COMPANY REGISTER PROFILE
930923559 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

LØVSLAND HOLDING AS

Org. no. 930923559 Limited company (AS) Kristiansand Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK 36,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

LØVSLAND HOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 930923559. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2023. 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 · 2025

Operating profit
NOK −1,000
▼ −111 %
Equity
NOK 36,000
▼ −4 %
Est. value
NOK 30,000

Financial health · 2025

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

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

Who owns LØVSLAND HOLDING AS?

LØVSLAND HOLDING AS
· NOK −1,000 profit

LØVSLAND HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LØVSLAND HOLDING AS own?

LØVSLAND HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LØVSLAND HOLDING AS

Who owns LØVSLAND HOLDING AS?

Per-Ove Løvsland is the largest registered owner, with 100.0%.

Where is LØVSLAND HOLDING AS based?

LØVSLAND HOLDING AS has its business address in Kristiansand S.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.