BIZTRAC BETA
Architectural activities

SIVILARKITEKT TORDIS HOEM AS

Org. no. 976501187 Limited company (AS) Oslo Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 339,000
Operating profit NOK −45,000
Equity NOK 41,000
Incorporated 1996
Share capital NOK 100,000

Signals

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

SIVILARKITEKT TORDIS HOEM AS is registered as a limited company in Oslo, Oslo with organisation number 976501187. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Å yte arkitekttjenester og hertil relaterte tjenester. Herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 339,000 in revenue and NOK −45,000 in operating profit.

Key figures · 2025

Revenue
NOK 339,000
Operating profit
NOK −45,000
Equity
NOK 41,000
Est. value
NOK 376,000

Financial health · 2025

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

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

Who owns SIVILARKITEKT TORDIS HOEM AS?

TORDIS GRØNSTAD HOEM
SIVILARKITEKT TORDIS HOEM AS
NOK 339,000 rev. · NOK −45,000 profit

SIVILARKITEKT TORDIS HOEM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIVILARKITEKT TORDIS HOEM AS

Who owns SIVILARKITEKT TORDIS HOEM AS?

TORDIS GRØNSTAD HOEM is the largest registered owner, with 100.0%.

What is the revenue of SIVILARKITEKT TORDIS HOEM AS?

SIVILARKITEKT TORDIS HOEM AS had revenue of NOK 339,000 in 2025.

Where is SIVILARKITEKT TORDIS HOEM AS based?

SIVILARKITEKT TORDIS HOEM 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.