BIZTRAC BETA
Rental and operating of own or leased real estate

LEVANGER BRYGGE EIENDOM AS

Org. no. 988985112 Limited company (AS) Stjørdal Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6,000
Equity NOK 459,000
Incorporated 2005
Share capital NOK 700,000

Signals

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

LEVANGER BRYGGE EIENDOM AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 988985112. 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 700,000, divided into 700 shares. The company's stated purpose is: “Kjøp, besittelse og salg av aksjer eller eiendommer, utleie av eiendommer og ellers det som naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 459,000
Est. value
NOK 419,000

Financial health · 2024

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

Who owns LEVANGER BRYGGE EIENDOM AS?

PLATON PROSJEKTUTVIKLING AS
LEVANGER BRYGGE EIENDOM AS
NOK 0 rev. · NOK −6,000 profit

LEVANGER BRYGGE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEVANGER BRYGGE EIENDOM AS

Who owns LEVANGER BRYGGE EIENDOM AS?

PLATON PROSJEKTUTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of LEVANGER BRYGGE EIENDOM AS?

LEVANGER BRYGGE EIENDOM AS had revenue of NOK 0 in 2024.

Where is LEVANGER BRYGGE EIENDOM AS based?

LEVANGER BRYGGE EIENDOM AS has its business address in Stjørdal.

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.