BIZTRAC BETA
Other technical consultancy

LILLEBAKK CONSULT AS

Org. no. 933253260 Limited company (AS) Hustadvika Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 161,000
Equity NOK 143,000
Incorporated 2024
Share capital NOK 30,000

LILLEBAKK CONSULT AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 933253260. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen ingeniørarbeid, og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 161,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 161,000
Equity
NOK 143,000
Est. value
NOK 866,000

Financial health · 2025

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

Who owns LILLEBAKK CONSULT AS?

SLIPSTEINSHAUGEN INVEST AS
LILLEBAKK CONSULT AS
NOK 1.0m rev. · NOK 161,000 profit

LILLEBAKK CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LILLEBAKK CONSULT AS

Who owns LILLEBAKK CONSULT AS?

SLIPSTEINSHAUGEN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of LILLEBAKK CONSULT AS?

LILLEBAKK CONSULT AS had revenue of NOK 1.0m in 2025.

Who is the general manager of LILLEBAKK CONSULT AS?

Andre Lillebakk is registered as general manager of LILLEBAKK CONSULT AS.

Where is LILLEBAKK CONSULT AS based?

LILLEBAKK CONSULT AS has its business address in Elnesvågen.

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.