BIZTRAC BETA
Rental and operating of own or leased real estate

LAUVSNESØRA AS

Org. no. 998619777 Limited company (AS) Flatanger Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 613,000
Operating profit NOK 215,000
Equity NOK 214,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

LAUVSNESØRA AS is registered as a limited company in Flatanger, Trøndelag with organisation number 998619777. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i fast eiendom og aksjer, herunder kjøp, salg, eie og utleie av fast eiendom, deltakelse i andre selskaper med sammenfallende formål, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 613,000 in revenue and NOK 215,000 in operating profit.

Key figures · 2024

Revenue
NOK 613,000
Operating profit
NOK 215,000
Equity
NOK 214,000
Est. value
NOK 378,000

Financial health · 2024

Liquidity
1.96
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.9%
Weak
Equity as a share of total capital

Who owns LAUVSNESØRA AS?

FANØYSKJÆRET AS
LAUVSNESØRA AS
NOK 613,000 rev. · NOK 215,000 profit

LAUVSNESØRA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAUVSNESØRA AS

Who owns LAUVSNESØRA AS?

FANØYSKJÆRET AS is the largest registered owner, with 100.0%.

What is the revenue of LAUVSNESØRA AS?

LAUVSNESØRA AS had revenue of NOK 613,000 in 2024.

Where is LAUVSNESØRA AS based?

LAUVSNESØRA AS has its business address in Flatanger.

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.