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

ERIK TVEIT SIVILARKITEKT AS

Org. no. 927710455 Limited company (AS) Kristiansand Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 288,000
Equity NOK 51,000
Incorporated 2021
Share capital NOK 30,000

ERIK TVEIT SIVILARKITEKT AS is registered as a limited company in Kristiansand, Agder with organisation number 927710455. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Arkitekt- og konsulentvirksomhet, investering i aksjer, kjøpe og selge samt eie fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 288,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
▲ +65 %
Operating profit
NOK 288,000
▲ +1807 %
Equity
NOK 51,000
▲ +18 %
Est. value
NOK 800,000

Financial health · 2025

Liquidity
1.10
Satisfactory
Current assets ÷ current liabilities
Profitability
62.1%
Very good
Return on total assets
Solidity
8.7%
Weak
Equity as a share of total capital

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

Who owns ERIK TVEIT SIVILARKITEKT AS?

ERIK TVEIT SIVILARKITEKT AS
NOK 1.0m rev. · NOK 288,000 profit

ERIK TVEIT SIVILARKITEKT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ERIK TVEIT SIVILARKITEKT AS

Who owns ERIK TVEIT SIVILARKITEKT AS?

KLOSS AS is the largest registered owner, with 100.0%.

What is the revenue of ERIK TVEIT SIVILARKITEKT AS?

ERIK TVEIT SIVILARKITEKT AS had revenue of NOK 1.0m in 2025.

Where is ERIK TVEIT SIVILARKITEKT AS based?

ERIK TVEIT SIVILARKITEKT AS has its business address in Kristiansand S.

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.