BIZTRAC BETA
COMPANY REGISTER PROFILE
925665150 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 02.09.2026
Retail sale of second-hand goods

HS BRUKT & ANTIKK AS

Org. no. 925665150 Limited company (AS) Tønsberg Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 91.8m
Operating profit NOK 16.7m
Equity NOK 19.0m
Incorporated 2020
Employees 6
Share capital NOK 30,000

HS BRUKT & ANTIKK AS is registered as a limited company in Tønsberg, Vestfold with organisation number 925665150. The business is classified under retail sale of second-hand goods (NACE 47.790). The company was incorporated in 2020 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av brukte gjenstander.”. The most recent filed accounts, for the 2025 financial year, show NOK 91.8m in revenue and NOK 16.7m in operating profit.

Key figures · 2025

Revenue
NOK 91.8m
▲ +153 %
Operating profit
NOK 16.7m
▲ +190 %
Equity
NOK 19.0m
▲ +215 %
Est. value
NOK 51.6m

Financial health · 2025

Liquidity
3.36
Very good
Current assets ÷ current liabilities
Profitability
92.9%
Very good
Return on total assets
Solidity
71.2%
Very good
Equity as a share of total capital

Who owns HS BRUKT & ANTIKK AS?

HS BRUKT & ANTIKK AS
NOK 91.8m rev. · NOK 16.7m profit

HS BRUKT & ANTIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HS BRUKT & ANTIKK AS

Who owns HS BRUKT & ANTIKK AS?

HAAKON GJERDRUM SIVERTSEN is the largest registered owner, with 100.0%.

What is the revenue of HS BRUKT & ANTIKK AS?

HS BRUKT & ANTIKK AS had revenue of NOK 91.8m in 2025.

Who is the general manager of HS BRUKT & ANTIKK AS?

Haakon Gjerdrum Sivertsen is registered as general manager of HS BRUKT & ANTIKK AS.

Where is HS BRUKT & ANTIKK AS based?

HS BRUKT & ANTIKK AS has its business address in Tønsberg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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