BIZTRAC BETA
Architectural activities

LPO ARKITEKTER AS

Org. no. 934007514 Limited company (AS) Oslo Incorporated 1983 Active
Ownership graph ↗
Revenue 2024 NOK 187.7m
Operating profit NOK 1.9m
Equity NOK 29.1m
Incorporated 1983
Employees 124
Share capital NOK 2.2m

LPO ARKITEKTER AS is registered as a limited company in Oslo, Oslo with organisation number 934007514. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 1983 and has 124 registered employees. Registered share capital is NOK 2.2m, divided into 22080 shares. The company's stated purpose is: “Arkitektvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 187.7m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 187.7m
Operating profit
NOK 1.9m
Equity
NOK 29.1m
Est. value
NOK 23.9m

Financial health · 2024

Liquidity
1.62
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
42.0%
Very good
Equity as a share of total capital

Who owns LPO ARKITEKTER AS?

LPO ARKITEKTER AS
LPO ARKITEKTER AS
NOK 187.7m rev. · NOK 1.9m profit

LPO ARKITEKTER AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does LPO ARKITEKTER AS own?

LPO ARKITEKTER AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

LPO ARKITEKTER AS er morselskap for 1 datterselskap:

Frequently asked questions about LPO ARKITEKTER AS

Who owns LPO ARKITEKTER AS?

LPO ARKITEKTER AS is the largest registered owner, with 2.1%.

What is the revenue of LPO ARKITEKTER AS?

LPO ARKITEKTER AS had revenue of NOK 187.7m in 2024.

Who is the general manager of LPO ARKITEKTER AS?

Øystein Sjøstrand is registered as general manager of LPO ARKITEKTER AS.

Where is LPO ARKITEKTER AS based?

LPO ARKITEKTER AS has its business address in Oslo.

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.