BIZTRAC BETA
Architectural activities

ARCHI BYGG AS

Org. no. 915137083 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK −137,000
Equity NOK 237,000
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−137k kr).
  • Nylig endring 2026-02-24 Adresseendring registrert 2026-02-24.

ARCHI BYGG AS is registered as a limited company in Oslo, Oslo with organisation number 915137083. 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 30000 shares. The company's stated purpose is: “Bygg, arkitektur og design.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK −137,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK −137,000
Equity
NOK 237,000
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns ARCHI BYGG AS?

SASIKASAN KUNARAJAH
ARCHI BYGG AS
NOK 2.0m rev. · NOK −137,000 profit

ARCHI BYGG AS has 3 registered shareholders:

All shareholders and roles →

Which companies does ARCHI BYGG AS own?

ARCHI BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ARCHI BYGG AS

Who owns ARCHI BYGG AS?

SASIKASAN KUNARAJAH is the largest registered owner, with 33.3%.

What is the revenue of ARCHI BYGG AS?

ARCHI BYGG AS had revenue of NOK 2.0m in 2024.

Who is the general manager of ARCHI BYGG AS?

Sasikasan Kunarajah is registered as general manager of ARCHI BYGG AS.

Where is ARCHI BYGG AS based?

ARCHI BYGG 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.