BIZTRAC BETA
Civil engineering activities

LODEWYCKX CONSULTING AS

Org. no. 932609738 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 227,000
Equity NOK 375,000
Incorporated 2023
Share capital NOK 30,000

LODEWYCKX CONSULTING AS is registered as a limited company in Bærum, Akershus with organisation number 932609738. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen byggteknisk konsulentvirksomhet 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.1m in revenue and NOK 227,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 227,000
Equity
NOK 375,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns LODEWYCKX CONSULTING AS?

INE LODEWYCKX
LODEWYCKX CONSULTING AS
NOK 1.1m rev. · NOK 227,000 profit

LODEWYCKX CONSULTING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LODEWYCKX CONSULTING AS

Who owns LODEWYCKX CONSULTING AS?

INE LODEWYCKX is the largest registered owner, with 75.0%.

What is the revenue of LODEWYCKX CONSULTING AS?

LODEWYCKX CONSULTING AS had revenue of NOK 1.1m in 2025.

Who is the general manager of LODEWYCKX CONSULTING AS?

Ine Lodewyckx is registered as general manager of LODEWYCKX CONSULTING AS.

Where is LODEWYCKX CONSULTING AS based?

LODEWYCKX CONSULTING AS has its business address in Eiksmarka.

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.