BIZTRAC BETA
Architectural activities

STEFAN EKBERG ARKITEKTER AS

Org. no. 915843352 Limited company (AS) Bærum Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 528,000
Operating profit NOK −250,000
Equity NOK 3.4m
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−250k kr).

STEFAN EKBERG ARKITEKTER AS is registered as a limited company in Bærum, Akershus with organisation number 915843352. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Arkitektur og rådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 528,000 in revenue and NOK −250,000 in operating profit.

Key figures · 2025

Revenue
NOK 528,000
Operating profit
NOK −250,000
Equity
NOK 3.4m
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns STEFAN EKBERG ARKITEKTER AS?

JAN STEFAN EKBERG
STEFAN EKBERG ARKITEKTER AS
NOK 528,000 rev. · NOK −250,000 profit

STEFAN EKBERG ARKITEKTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STEFAN EKBERG ARKITEKTER AS

Who owns STEFAN EKBERG ARKITEKTER AS?

JAN STEFAN EKBERG is the largest registered owner, with 100.0%.

What is the revenue of STEFAN EKBERG ARKITEKTER AS?

STEFAN EKBERG ARKITEKTER AS had revenue of NOK 528,000 in 2025.

Who is the general manager of STEFAN EKBERG ARKITEKTER AS?

Jan Stefan Ekberg is registered as general manager of STEFAN EKBERG ARKITEKTER AS.

Where is STEFAN EKBERG ARKITEKTER AS based?

STEFAN EKBERG ARKITEKTER AS has its business address in Bekkestua.

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.