biztrac. BETA
COMPANY REGISTER PROFILE
915752071 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of cultural and recreational goods n.e.c.

FREMMEDART AS

Org. no. 915752071 Limited company (AS) Horten Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 755,000
Operating profit NOK 231,000
Equity NOK 576,000
Incorporated 2015
Share capital NOK 30,000

FREMMEDART AS is registered as a limited company in Horten, Vestfold with organisation number 915752071. The business is classified under retail sale of cultural and recreational goods n.e.c. (NACE 47.690). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Billedkunst, fotografi, galleri, konferansesenterdrift, kurs, aktivitetssenter, cafedrift, souvenirbutikk og mer.”. The most recent filed accounts, for the 2025 financial year, show NOK 755,000 in revenue and NOK 231,000 in operating profit.

Key figures · 2025

Revenue
NOK 755,000
▼ −8 %
Operating profit
NOK 231,000
▼ −17 %
Equity
NOK 576,000
▲ +60 %
Est. value
NOK 913,000

Financial health · 2025

Liquidity
-10.41
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
23.7%
Good
Equity as a share of total capital

Who owns FREMMEDART AS?

FREMMEDART AS
NOK 755,000 rev. · NOK 231,000 profit

FREMMEDART AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FREMMEDART AS

Who owns FREMMEDART AS?

Galina Manikova is the largest registered owner, with 100.0%.

What is the revenue of FREMMEDART AS?

FREMMEDART AS had revenue of NOK 755,000 in 2025.

Who is the general manager of FREMMEDART AS?

Galina Manikova is registered as general manager of FREMMEDART AS.

Where is FREMMEDART AS based?

FREMMEDART AS has its business address in Horten.

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.