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

ROJO ARKITEKTER AS

Org. no. 951770930 Limited company (AS) Trondheim Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 11.7m
Operating profit NOK 2.2m
Equity NOK 2.6m
Incorporated 1989
Employees 8
Share capital NOK 100,000

ROJO ARKITEKTER AS is registered as a limited company in Trondheim, Trøndelag with organisation number 951770930. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 1989 and has 8 registered employees. Registered share capital is NOK 100,000. The company's stated purpose is: “Produsere og markedsføre tjenester innen arkitekt- faget og hva dermed står i forbindelse, samt ved aksjetegning eller på annet vis delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.7m in revenue and NOK 2.2m in operating profit.

Former names: ROJO AS

Key figures · 2025

Revenue
NOK 11.7m
▼ −2 %
Operating profit
NOK 2.2m
▼ −19 %
Equity
NOK 2.6m
▲ +1 %
Est. value
NOK 11.3m

Financial health · 2025

Liquidity
1.52
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
38.2%
Good
Equity as a share of total capital

Who owns ROJO ARKITEKTER AS?

ROJO ARKITEKTER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ROJO ARKITEKTER AS

Who owns ROJO ARKITEKTER AS?

SONEN AS is the largest registered owner, with 34.0%.

What is the revenue of ROJO ARKITEKTER AS?

ROJO ARKITEKTER AS had revenue of NOK 11.7m in 2025.

Who is the general manager of ROJO ARKITEKTER AS?

Sondre-Niclas Andvik is registered as general manager of ROJO ARKITEKTER AS.

Where is ROJO ARKITEKTER AS based?

ROJO ARKITEKTER AS has its business address in Trondheim.

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.