BIZTRAC BETA
COMPANY REGISTER PROFILE
914041902 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

LOGL AS

Org. no. 914041902 Limited company (AS) Øygarden Incorporated 2014 Active
Ownership graph ↗
Equity NOK −888,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−888k kr).

LOGL AS is registered as a limited company in Øygarden, Vestland with organisation number 914041902. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg og utvikling av tomter og eiendommer.”.

Key figures · 2025

Equity
NOK −888,000
▲ +2 %

Financial health · 2025

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

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

Who owns LOGL AS?

LOGL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LOGL AS own?

LOGL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LOGL AS

Who owns LOGL AS?

MORTEN LANDRO is the largest registered owner, with 100.0%.

Where is LOGL AS based?

LOGL AS has its business address in Ågotnes.

Property

Business address Solsvikvegen 28, 5363 Ågotnes
Cadastral unit 4626-25/70/0/0
Building Enebolig · 1 unit

3 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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