BIZTRAC BETA
Rental and operating of own or leased real estate

LASCALA CONSULTING AS

Org. no. 989087940 Limited company (AS) Porsgrunn Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK 25,000
Equity NOK 95.2m
Incorporated 2005
Share capital NOK 2.3m

LASCALA CONSULTING AS is registered as a limited company in Porsgrunn, Telemark with organisation number 989087940. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 2.3m, divided into 2292 shares. The company's stated purpose is: “Finans- og realobjekter og forvaltning av disse. Drive handelsvirksomhet, herunder eksport og konsulentvirksomhet i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK 25,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK 25,000
Equity
NOK 95.2m
Est. value
NOK 66.0m

Financial health · 2024

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

Who owns LASCALA CONSULTING AS?

JAN KVIDALAND
LASCALA CONSULTING AS
NOK 1.0m rev. · NOK 25,000 profit

LASCALA CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LASCALA CONSULTING AS own?

LASCALA CONSULTING AS holds stakes in 11 companies:

See the full ownership structure →

Frequently asked questions about LASCALA CONSULTING AS

Who owns LASCALA CONSULTING AS?

JAN KVIDALAND is the largest registered owner, with 100.0%.

What is the revenue of LASCALA CONSULTING AS?

LASCALA CONSULTING AS had revenue of NOK 1.0m in 2024.

Where is LASCALA CONSULTING AS based?

LASCALA CONSULTING AS has its business address in Porsgrunn.

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.