BIZTRAC BETA
Rental and operating of own or leased real estate

LYNGTUN BREIVIKA AS

Org. no. 917141002 Limited company (AS) Ålesund Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 2.2m
Equity NOK 13.4m
Incorporated 2016
Share capital NOK 165,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LYNGTUN BREIVIKA AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 917141002. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 165,000, divided into 165324 shares. The company's stated purpose is: “Kjøp og salg av fast eiendom, herunder utleie, deltakelse i andre selskaper og annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 2.2m
Equity
NOK 13.4m
Est. value
NOK 14.7m

Financial health · 2025

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

Who owns LYNGTUN BREIVIKA AS?

LYNGTUN HOLDING AS
LYNGTUN BREIVIKA AS
NOK 3.1m rev. · NOK 2.2m profit

LYNGTUN BREIVIKA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LYNGTUN BREIVIKA AS

Who owns LYNGTUN BREIVIKA AS?

LYNGTUN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LYNGTUN BREIVIKA AS?

LYNGTUN BREIVIKA AS had revenue of NOK 3.1m in 2025.

Where is LYNGTUN BREIVIKA AS based?

LYNGTUN BREIVIKA AS has its business address in Ålesund.

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.