biztrac. BETA
COMPANY REGISTER PROFILE
914185521 ORG. NO. 2022 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of second-hand goods

STORE MÆLA GÅRD ANTIK DA

Org. no. 914185521 General partnership with shared liability (DA) Skien Incorporated 2014 Active
Revenue 2022 NOK 1.2m
Operating profit NOK 126,000
Equity NOK 0
Incorporated 2014

STORE MÆLA GÅRD ANTIK DA is registered as a general partnership with shared liability in Skien, Telemark with organisation number 914185521. The business is classified under retail sale of second-hand goods (NACE 47.790). The company was incorporated in 2014. The company's stated purpose is: “Kjøp og salg av antikviteter, kunst og brukt. Oppkjøp av dødsbo. Opprydding av hus og gard. Auksjonssalg.”. The most recent filed accounts, for the 2022 financial year, show NOK 1.2m in revenue and NOK 126,000 in operating profit.

Former names: VIKING EMPIRE ANTIKK & BRUKT DA

Key figures · 2022

Revenue
NOK 1.2m
▲ +7 %
Operating profit
NOK 126,000
▲ +512 %
Equity
NOK 0
Est. value
NOK 617,000

Financial health · 2022

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

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

Who owns STORE MÆLA GÅRD ANTIK DA?

No shareholders are registered for STORE MÆLA GÅRD ANTIK DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STORE MÆLA GÅRD ANTIK DA

What is the revenue of STORE MÆLA GÅRD ANTIK DA?

STORE MÆLA GÅRD ANTIK DA had revenue of NOK 1.2m in 2022.

Who is the general manager of STORE MÆLA GÅRD ANTIK DA?

Egil Olav Kveum is registered as general manager of STORE MÆLA GÅRD ANTIK DA.

Where is STORE MÆLA GÅRD ANTIK DA based?

STORE MÆLA GÅRD ANTIK DA has its business address in Skien.

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

Report a problem

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