BIZTRAC BETA
Joinery installation

LOGA INNREDNINGER AS

Org. no. 932847361 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 195,000
Operating profit NOK 19,000
Equity NOK 71,000
Incorporated 2023
Share capital NOK 100,000

LOGA INNREDNINGER AS is registered as a limited company in Bærum, Akershus with organisation number 932847361. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive produksjon og montering av innredninger, samt dertil tilhørende tømrertjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 195,000 in revenue and NOK 19,000 in operating profit.

Key figures · 2025

Revenue
NOK 195,000
Operating profit
NOK 19,000
Equity
NOK 71,000
Est. value
NOK 84,000

Financial health · 2025

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

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

Who owns LOGA INNREDNINGER AS?

OLE LOGA AS
LOGA INNREDNINGER AS
NOK 195,000 rev. · NOK 19,000 profit

LOGA INNREDNINGER AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LOGA INNREDNINGER AS er morselskap for 1 datterselskap:

Frequently asked questions about LOGA INNREDNINGER AS

Who owns LOGA INNREDNINGER AS?

OLE LOGA AS is the largest registered owner, with 100.0%.

What is the revenue of LOGA INNREDNINGER AS?

LOGA INNREDNINGER AS had revenue of NOK 195,000 in 2025.

Who is the general manager of LOGA INNREDNINGER AS?

Ole Loga is registered as general manager of LOGA INNREDNINGER AS.

Where is LOGA INNREDNINGER AS based?

LOGA INNREDNINGER AS has its business address in Lysaker.

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.