BIZTRAC BETA
Buying and selling of own real estate

HJØRNET 3 AS

Org. no. 919794119 Limited company (AS) Kristiansand Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 31,000
Operating profit NOK −37,000
Equity NOK −58,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−58k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−37k kr).

HJØRNET 3 AS is registered as a limited company in Kristiansand, Agder with organisation number 919794119. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie og drift av eiendommer og det som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 31,000 in revenue and NOK −37,000 in operating profit.

Key figures · 2024

Revenue
NOK 31,000
Operating profit
NOK −37,000
Equity
NOK −58,000

Financial health · 2024

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

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

Who owns HJØRNET 3 AS?

TROND ERIK BYREMO
HJØRNET 3 AS
NOK 31,000 rev. · NOK −37,000 profit

HJØRNET 3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HJØRNET 3 AS

Who owns HJØRNET 3 AS?

TROND ERIK BYREMO is the largest registered owner, with 100.0%.

What is the revenue of HJØRNET 3 AS?

HJØRNET 3 AS had revenue of NOK 31,000 in 2024.

Who is the general manager of HJØRNET 3 AS?

Trond Erik Byremo is registered as general manager of HJØRNET 3 AS.

Where is HJØRNET 3 AS based?

HJØRNET 3 AS has its business address in Mosby.

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.