BIZTRAC BETA
Other technical consultancy

LK-CONSULTING AS

Org. no. 921039840 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 172,000
Operating profit NOK 54,000
Equity NOK 677,000
Incorporated 2018
Share capital NOK 30,000

LK-CONSULTING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 921039840. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet, prosjektutvikling, investeringsvirksomhet, eiendomsforvaltning og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 172,000 in revenue and NOK 54,000 in operating profit.

Key figures · 2025

Revenue
NOK 172,000
Operating profit
NOK 54,000
Equity
NOK 677,000
Est. value
NOK 604,000

Financial health · 2025

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

Who owns LK-CONSULTING AS?

LARS KILAAS
LK-CONSULTING AS
NOK 172,000 rev. · NOK 54,000 profit

LK-CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LK-CONSULTING AS own?

LK-CONSULTING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LK-CONSULTING AS

Who owns LK-CONSULTING AS?

LARS KILAAS is the largest registered owner, with 100.0%.

What is the revenue of LK-CONSULTING AS?

LK-CONSULTING AS had revenue of NOK 172,000 in 2025.

Who is the general manager of LK-CONSULTING AS?

Lars Kilaas is registered as general manager of LK-CONSULTING AS.

Where is LK-CONSULTING AS based?

LK-CONSULTING AS has its business address in Trondheim.

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.