BIZTRAC BETA
Architectural activities

EKBERG LOUS ARKITEKTER AS

Org. no. 992932716 Limited company (AS) Asker Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 139,000
Equity NOK 164,000
Incorporated 2008
Share capital NOK 100,000

EKBERG LOUS ARKITEKTER AS is registered as a limited company in Asker, Akershus with organisation number 992932716. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Arkitekttjenester samt andre konsultative tjenester som står i denne forbindelse, herunder også deltakelse i annen næringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 139,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 139,000
Equity
NOK 164,000
Est. value
NOK 789,000

Financial health · 2024

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

Who owns EKBERG LOUS ARKITEKTER AS?

MALIN MARIA EKBERG LOUS
EKBERG LOUS ARKITEKTER AS
NOK 1.1m rev. · NOK 139,000 profit

EKBERG LOUS ARKITEKTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EKBERG LOUS ARKITEKTER AS

Who owns EKBERG LOUS ARKITEKTER AS?

MALIN MARIA EKBERG LOUS is the largest registered owner, with 50.0%.

What is the revenue of EKBERG LOUS ARKITEKTER AS?

EKBERG LOUS ARKITEKTER AS had revenue of NOK 1.1m in 2024.

Who is the general manager of EKBERG LOUS ARKITEKTER AS?

Henrik Ekberg Lous is registered as general manager of EKBERG LOUS ARKITEKTER AS.

Where is EKBERG LOUS ARKITEKTER AS based?

EKBERG LOUS ARKITEKTER AS has its business address in Borgen.

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.