biztrac. BETA
COMPANY REGISTER PROFILE
912886646 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

LANGØY EIENDOM AS

Org. no. 912886646 Limited company (AS) Øygarden Incorporated 2013 Active
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 22,000
Incorporated 2013
Share capital NOK 30,000

Signals

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

LANGØY EIENDOM AS is registered as a limited company in Øygarden, Vestland with organisation number 912886646. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Utvikle eiendom for salg.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
▼ −56 %
Equity
NOK 22,000
▼ −18 %
Est. value
NOK 20,000

Financial health · 2025

Liquidity
8.25
Very good
Current assets ÷ current liabilities
Profitability
-18.8%
Not satisfactory
Return on total assets
Solidity
87.9%
Weak
Equity as a share of total capital

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

Who owns LANGØY EIENDOM AS?

LANGØY EIENDOM AS
NOK 0 rev. · NOK −5,000 profit

LANGØY EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LANGØY EIENDOM AS

Who owns LANGØY EIENDOM AS?

Birger Løvland is the largest registered owner, with 100.0%.

What is the revenue of LANGØY EIENDOM AS?

LANGØY EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of LANGØY EIENDOM AS?

Birger Løvland is registered as general manager of LANGØY EIENDOM AS.

Where is LANGØY EIENDOM AS based?

LANGØY EIENDOM AS has its business address in Fjell.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.