BIZTRAC BETA
Rental and operating of own or leased real estate

HJEMSENG BRYGGE AS

Org. no. 920576338 Limited company (AS) Tønsberg Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −2.9m
Equity NOK 44.4m
Incorporated 2017
Share capital NOK 150,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,9 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HJEMSENG BRYGGE AS is registered as a limited company in Tønsberg, Vestfold with organisation number 920576338. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 150,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utvikling av fast eiendom, samt all annen virksomhet som har tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −2.9m in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −2.9m
Equity
NOK 44.4m
Est. value
NOK 40.5m

Financial health · 2024

Liquidity
11.67
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.9%
Good
Equity as a share of total capital

Who owns HJEMSENG BRYGGE AS?

KAUPANG INVEST AS
HJEMSENG BRYGGE AS
NOK 1.1m rev. · NOK −2.9m profit

HJEMSENG BRYGGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HJEMSENG BRYGGE AS

Who owns HJEMSENG BRYGGE AS?

KAUPANG INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of HJEMSENG BRYGGE AS?

HJEMSENG BRYGGE AS had revenue of NOK 1.1m in 2024.

Where is HJEMSENG BRYGGE AS based?

HJEMSENG BRYGGE AS has its business address in Sem.

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.