BIZTRAC BETA
Business and other management consultancy activities

LODESTONE CONSULTING AS

Org. no. 930162647 Limited company (AS) Tønsberg Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 166,000
Equity NOK 14,000
Incorporated 2022
Share capital NOK 30,000

LODESTONE CONSULTING AS is registered as a limited company in Tønsberg, Vestfold with organisation number 930162647. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drive rådgivende virksomhet og levere konsulent- og utdanningstjenester innen maritim industri, herunder samarbeide med, delta i, eller opprette andre selskaper som har naturlig sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 166,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 166,000
Equity
NOK 14,000
Est. value
NOK 407,000

Financial health · 2025

Liquidity
1.69
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.8%
Weak
Equity as a share of total capital

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

Who owns LODESTONE CONSULTING AS?

LARS BAUST KLEMMETSBY
LODESTONE CONSULTING AS
NOK 3.0m rev. · NOK 166,000 profit

LODESTONE CONSULTING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LODESTONE CONSULTING AS

Who owns LODESTONE CONSULTING AS?

LARS BAUST KLEMMETSBY is the largest registered owner, with 50.0%.

What is the revenue of LODESTONE CONSULTING AS?

LODESTONE CONSULTING AS had revenue of NOK 3.0m in 2025.

Where is LODESTONE CONSULTING AS based?

LODESTONE CONSULTING AS has its business address in Barkåker.

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.