biztrac. BETA
COMPANY REGISTER PROFILE
912738418 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠LU CONSULT AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Other technical consultancy

LU CONSULT AS

Org. no. 912738418 Limited company (AS) Asker Incorporated 2013 In liquidation
Revenue 2025 NOK 83,000
Operating profit NOK −416,000
Equity NOK 301,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

LU CONSULT AS is registered as a limited company in Asker, Akershus with organisation number 912738418. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Yte maritime og marinetekniske rådgivnings- og servicetjenester til olje- og skipsindustrien, og investere og handle med aksjer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 83,000 in revenue and NOK −416,000 in operating profit.

Key figures · 2025

Revenue
NOK 83,000
▼ −74 %
Operating profit
NOK −416,000
▼ −3878 %
Equity
NOK 301,000
▼ −51 %

Financial health · 2025

Liquidity
3.93
Very good
Current assets ÷ current liabilities
Profitability
-64.8%
Not satisfactory
Return on total assets
Solidity
77.8%
Very good
Equity as a share of total capital

Who owns LU CONSULT AS?

LU CONSULT AS
NOK 83,000 rev. · NOK −416,000 profit

LU CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LU CONSULT AS

Who owns LU CONSULT AS?

Johan Lassen-Urdahl is the largest registered owner, with 100.0%.

What is the revenue of LU CONSULT AS?

LU CONSULT AS had revenue of NOK 83,000 in 2025.

Where is LU CONSULT AS based?

LU CONSULT AS has its business address in Vollen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.