BIZTRAC BETA
Rental and operating of own or leased real estate

HUSVÆR BRYGGE AS

Org. no. 915341888 Limited company (AS) Kristiansand Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 449,000
Operating profit NOK −61,000
Equity NOK 490,000
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−61k kr).
  • Nylig endring 2026-02-06 Adresseendring registrert 2026-02-06.

HUSVÆR BRYGGE AS is registered as a limited company in Kristiansand, Agder with organisation number 915341888. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eiendomsselskap og skal drive virksomhet med kjøp, utvikling, forvaltning og utleie av fast eiendom og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 449,000 in revenue and NOK −61,000 in operating profit.

Key figures · 2025

Revenue
NOK 449,000
Operating profit
NOK −61,000
Equity
NOK 490,000
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
0.22
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
63.2%
Very good
Equity as a share of total capital

Who owns HUSVÆR BRYGGE AS?

TORGHATTEN EIENDOM AS
HUSVÆR BRYGGE AS
NOK 449,000 rev. · NOK −61,000 profit

HUSVÆR BRYGGE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HUSVÆR BRYGGE AS

Who owns HUSVÆR BRYGGE AS?

TORGHATTEN EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of HUSVÆR BRYGGE AS?

HUSVÆR BRYGGE AS had revenue of NOK 449,000 in 2025.

Where is HUSVÆR BRYGGE AS based?

HUSVÆR BRYGGE 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.