BIZTRAC BETA
Development of building projects

LEGALETT NORGE AS

Org. no. 931986783 Limited company (AS) Hvaler Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 606,000
Operating profit NOK 3,000
Equity NOK 60,000
Incorporated 2023
Share capital NOK 50,000

LEGALETT NORGE AS is registered as a limited company in Hvaler, Østfold with organisation number 931986783. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Selge varer og tjenester innen byggeprosjekter 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 606,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2025

Revenue
NOK 606,000
Operating profit
NOK 3,000
Equity
NOK 60,000
Est. value
NOK 48,000

Financial health · 2025

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LEGALETT NORGE AS?

LASSE HEGGEDAL
LEGALETT NORGE AS
NOK 606,000 rev. · NOK 3,000 profit

LEGALETT NORGE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LEGALETT NORGE AS

Who owns LEGALETT NORGE AS?

LASSE HEGGEDAL is the largest registered owner, with 25.0%.

What is the revenue of LEGALETT NORGE AS?

LEGALETT NORGE AS had revenue of NOK 606,000 in 2025.

Who is the general manager of LEGALETT NORGE AS?

Lasse Heggedal is registered as general manager of LEGALETT NORGE AS.

Where is LEGALETT NORGE AS based?

LEGALETT NORGE AS has its business address in Skjærhalden.

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.