BIZTRAC BETA
Retail sale of second-hand goods

ANTIK OG BRUKT CENTRALEN AS

Org. no. 921336217 Limited company (AS) Fredrikstad Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 4.0m
Operating profit NOK 474,000
Equity NOK 1.7m
Incorporated 2018
Employees 6
Share capital NOK 30,000

ANTIK OG BRUKT CENTRALEN AS is registered as a limited company in Fredrikstad, Østfold with organisation number 921336217. The business is classified under retail sale of second-hand goods (NACE 47.790). The company was incorporated in 2018 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Transport på veg, rydding, rengjøring. Brukthandel.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.0m in revenue and NOK 474,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.0m
Operating profit
NOK 474,000
Equity
NOK 1.7m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns ANTIK OG BRUKT CENTRALEN AS?

JOHN MICHAEL SHAW
ANTIK OG BRUKT CENTRALEN AS
NOK 4.0m rev. · NOK 474,000 profit

ANTIK OG BRUKT CENTRALEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ANTIK OG BRUKT CENTRALEN AS

Who owns ANTIK OG BRUKT CENTRALEN AS?

JOHN MICHAEL SHAW is the largest registered owner, with 100.0%.

What is the revenue of ANTIK OG BRUKT CENTRALEN AS?

ANTIK OG BRUKT CENTRALEN AS had revenue of NOK 4.0m in 2024.

Who is the general manager of ANTIK OG BRUKT CENTRALEN AS?

John Michael Shaw is registered as general manager of ANTIK OG BRUKT CENTRALEN AS.

Where is ANTIK OG BRUKT CENTRALEN AS based?

ANTIK OG BRUKT CENTRALEN AS has its business address in Gressvik.

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.