BIZTRAC BETA
Development of building projects

LØVVIK EIENDOM AS

Org. no. 997855469 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 228,000
Incorporated 2012
Share capital NOK 90,000

Signals

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

LØVVIK EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 997855469. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2012. Registered share capital is NOK 90,000, divided into 3000 shares. The company's stated purpose is: “Utvikling, kjøp, salg og forvaltning av fast eiendom, investering i ulike aktiva, samt annen beslektet virksomhet, herunder eie andeler i selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 228,000
Est. value
NOK 5.7m

Financial health · 2025

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

Who owns LØVVIK EIENDOM AS?

KJETIL LØVVIK
LØVVIK EIENDOM AS
NOK 0 rev. · NOK −13,000 profit

LØVVIK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LØVVIK EIENDOM AS own?

LØVVIK EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LØVVIK EIENDOM AS

Who owns LØVVIK EIENDOM AS?

KJETIL LØVVIK is the largest registered owner, with 100.0%.

What is the revenue of LØVVIK EIENDOM AS?

LØVVIK EIENDOM AS had revenue of NOK 0 in 2025.

Where is LØVVIK EIENDOM AS based?

LØVVIK EIENDOM 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.