BIZTRAC BETA
Rental and operating of own or leased real estate

LØKKEN-INVEST AS

Org. no. 989266144 Limited company (AS) Ringsaker Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 134,000
Operating profit NOK 32,000
Equity NOK 6.0m
Incorporated 2005
Share capital NOK 175,000

LØKKEN-INVEST AS is registered as a limited company in Ringsaker, Innlandet with organisation number 989266144. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 175,000, divided into 35 shares. The company's stated purpose is: “Investering i aksjer og eiendom og hva som herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 134,000 in revenue and NOK 32,000 in operating profit.

Key figures · 2024

Revenue
NOK 134,000
Operating profit
NOK 32,000
Equity
NOK 6.0m
Est. value
NOK 4.2m

Financial health · 2024

Liquidity
73.93
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
90.0%
Very good
Equity as a share of total capital

Who owns LØKKEN-INVEST AS?

SVEIN TORE LØKKEN
LØKKEN-INVEST AS
NOK 134,000 rev. · NOK 32,000 profit

LØKKEN-INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LØKKEN-INVEST AS own?

LØKKEN-INVEST AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about LØKKEN-INVEST AS

Who owns LØKKEN-INVEST AS?

SVEIN TORE LØKKEN is the largest registered owner, with 100.0%.

What is the revenue of LØKKEN-INVEST AS?

LØKKEN-INVEST AS had revenue of NOK 134,000 in 2024.

Who is the general manager of LØKKEN-INVEST AS?

Svein Tore Løkken is registered as general manager of LØKKEN-INVEST AS.

Where is LØKKEN-INVEST AS based?

LØKKEN-INVEST AS has its business address in Moelv.

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.