BIZTRAC BETA
Business and other management consultancy activities

LOKE CONSULTING AS

Org. no. 933753816 Limited company (AS) Sarpsborg Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 60,000
Operating profit NOK 47,000
Equity NOK 82,000
Incorporated 2024
Share capital NOK 30,000

LOKE CONSULTING AS is registered as a limited company in Sarpsborg, Østfold with organisation number 933753816. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bedriftsrådgivning og investering i andre foretak og fast eiendom samt det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 60,000 in revenue and NOK 47,000 in operating profit.

Key figures · 2025

Revenue
NOK 60,000
Operating profit
NOK 47,000
Equity
NOK 82,000
Est. value
NOK 206,000

Financial health · 2024

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 LOKE CONSULTING AS?

PETTER HEIDE LARSEN
LOKE CONSULTING AS
NOK 60,000 rev. · NOK 47,000 profit

LOKE CONSULTING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LOKE CONSULTING AS

Who owns LOKE CONSULTING AS?

PETTER HEIDE LARSEN is the largest registered owner, with 60.0%.

What is the revenue of LOKE CONSULTING AS?

LOKE CONSULTING AS had revenue of NOK 60,000 in 2025.

Who is the general manager of LOKE CONSULTING AS?

Petter Heide Larsen is registered as general manager of LOKE CONSULTING AS.

Where is LOKE CONSULTING AS based?

LOKE CONSULTING AS has its business address in Sarpsborg.

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.