BIZTRAC BETA
COMPANY REGISTER PROFILE
934570332 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

LONGLOG INVEST AS

Org. no. 934570332 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK 367
Equity NOK 367
Incorporated 2024
Share capital NOK 30,000

LONGLOG INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 934570332. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 900 shares. The company's stated purpose is: “Kjøp og salg av fast eiendom, samt naturlig tilhørende virksomhet.”.

Former names: ALFANOR 24091 AS

Key figures · 2025

Operating profit
NOK 367
Equity
NOK 367
Est. value
NOK 1,000

Financial health · 2025

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

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

Who owns LONGLOG INVEST AS?

LONGLOG INVEST AS
· NOK 367 profit

LONGLOG INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LONGLOG INVEST AS

Who owns LONGLOG INVEST AS?

JONAS BONNE ØYRI is the largest registered owner, with 100.0%.

Where is LONGLOG INVEST AS based?

LONGLOG INVEST AS has its business address in Fornebu.

Property

Business address Lilleruts vei 19, 1364 Fornebu
Cadastral unit 3201-41/933/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.