biztrac. BETA
COMPANY REGISTER PROFILE
995294117 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Architectural activities

KEY ARKITEKTER AS

Org. no. 995294117 Limited company (AS) Oslo Incorporated 2010 Active
Revenue 2025 NOK 796,000
Operating profit NOK −24,000
Equity NOK 3,000
Incorporated 2010
Share capital NOK 102,000

Signals

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

KEY ARKITEKTER AS is registered as a limited company in Oslo, Oslo with organisation number 995294117. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2010. Registered share capital is NOK 102,000, divided into 1020 shares. The company's stated purpose is: “Arkitektvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 796,000 in revenue and NOK −24,000 in operating profit.

Key figures · 2025

Revenue
NOK 796,000
▲ +124 %
Operating profit
NOK −24,000
▼ −2800 %
Equity
NOK 3,000
▼ −88 %
Est. value
NOK 14,000

Financial health · 2025

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

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

Who owns KEY ARKITEKTER AS?

KEY ARKITEKTER AS
NOK 796,000 rev. · NOK −24,000 profit

KEY ARKITEKTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KEY ARKITEKTER AS

Who owns KEY ARKITEKTER AS?

Kjetil Sæterdal is the largest registered owner, with 50.0%.

What is the revenue of KEY ARKITEKTER AS?

KEY ARKITEKTER AS had revenue of NOK 796,000 in 2025.

Who is the general manager of KEY ARKITEKTER AS?

Einar Hjeldnes is registered as general manager of KEY ARKITEKTER AS.

Where is KEY ARKITEKTER AS based?

KEY 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.