BIZTRAC BETA
Rental and operating of own or leased real estate

LESIGN EIENDOM AS

Org. no. 832803952 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 118,000
Operating profit NOK −5,000
Equity NOK 2.5m
Incorporated 2023
Share capital NOK 2.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5k kr).

LESIGN EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 832803952. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 2.0m, divided into 2000000 shares. The company's stated purpose is: “Selge varer og tjenester innen utleie av fast eiendom og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 118,000 in revenue and NOK −5,000 in operating profit.

Key figures · 2024

Revenue
NOK 118,000
Operating profit
NOK −5,000
Equity
NOK 2.5m
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns LESIGN EIENDOM AS?

LESIGN AS
LESIGN EIENDOM AS
NOK 118,000 rev. · NOK −5,000 profit

LESIGN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LESIGN EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about LESIGN EIENDOM AS

Who owns LESIGN EIENDOM AS?

LESIGN AS is the largest registered owner, with 100.0%.

What is the revenue of LESIGN EIENDOM AS?

LESIGN EIENDOM AS had revenue of NOK 118,000 in 2024.

Where is LESIGN EIENDOM AS based?

LESIGN EIENDOM AS has its business address in Godvik.

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.