BIZTRAC BETA
Site preparation

JAN-TORE LØKKE AS

Org. no. 928238393 Limited company (AS) Indre Østfold Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 808,000
Operating profit NOK 41,000
Equity NOK 78,000
Incorporated 2021
Share capital NOK 30,000

JAN-TORE LØKKE AS is registered as a limited company in Indre Østfold, Østfold with organisation number 928238393. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Entrepenørvirksomhet, herunder snørydding, gravearbeider, bygg og anleggsvirksomhet. Kjøp og salg av varer og tjenester som naturlig knytter seg til hovedvirksomheten. Kjøp, salg og utleie av maskiner.”. The most recent filed accounts, for the 2025 financial year, show NOK 808,000 in revenue and NOK 41,000 in operating profit.

Key figures · 2025

Revenue
NOK 808,000
Operating profit
NOK 41,000
Equity
NOK 78,000
Est. value
NOK 127,000

Financial health · 2025

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

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

Who owns JAN-TORE LØKKE AS?

JAN TORE LØKKE
JAN-TORE LØKKE AS
NOK 808,000 rev. · NOK 41,000 profit

JAN-TORE LØKKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JAN-TORE LØKKE AS

Who owns JAN-TORE LØKKE AS?

JAN TORE LØKKE is the largest registered owner, with 100.0%.

What is the revenue of JAN-TORE LØKKE AS?

JAN-TORE LØKKE AS had revenue of NOK 808,000 in 2025.

Who is the general manager of JAN-TORE LØKKE AS?

Jan Tore Løkke is registered as general manager of JAN-TORE LØKKE AS.

Where is JAN-TORE LØKKE AS based?

JAN-TORE LØKKE AS has its business address in Eidsberg.

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.