BIZTRAC BETA
Architectural activities

BRIIS ARKITEKTUR AS

Org. no. 927876175 Limited company (AS) Bærum Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 74,000
Equity NOK 131,000
Incorporated 2021
Share capital NOK 30,000

BRIIS ARKITEKTUR AS is registered as a limited company in Bærum, Akershus with organisation number 927876175. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Arkitektvirksomhet og eiendomsutvikling, samt annen virksomhet som naturlig faller inn under dette. Herunder å eie eller delta på annen måte i selskap innenfor samme eller tilgrensende virksomhetsområder.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 74,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 74,000
Equity
NOK 131,000
Est. value
NOK 434,000

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.5%
Good
Equity as a share of total capital

Who owns BRIIS ARKITEKTUR AS?

GLENN ALEXANDER BIRKELAND BJØRNSSON
BRIIS ARKITEKTUR AS
NOK 2.6m rev. · NOK 74,000 profit

BRIIS ARKITEKTUR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRIIS ARKITEKTUR AS

Who owns BRIIS ARKITEKTUR AS?

GLENN ALEXANDER BIRKELAND BJØRNSSON is the largest registered owner, with 50.0%.

What is the revenue of BRIIS ARKITEKTUR AS?

BRIIS ARKITEKTUR AS had revenue of NOK 2.6m in 2025.

Who is the general manager of BRIIS ARKITEKTUR AS?

Inge Berger Müller is registered as general manager of BRIIS ARKITEKTUR AS.

Where is BRIIS ARKITEKTUR AS based?

BRIIS ARKITEKTUR AS has its business address in Gjettum.

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.