BIZTRAC BETA
Activities of advertising agencies

SELEKTIV MARKEDSFØRING AS

Org. no. 993819220 Limited company (AS) Vegårshei Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 146,000
Operating profit NOK 34,000
Equity NOK 513,000
Incorporated 2009
Share capital NOK 100,000

SELEKTIV MARKEDSFØRING AS is registered as a limited company in Vegårshei, Agder with organisation number 993819220. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av skrapelodd, grafisk formidling, konsulenttjenester innenfor direkte markedsføring, og annen handelsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 146,000 in revenue and NOK 34,000 in operating profit.

Key figures · 2025

Revenue
NOK 146,000
Operating profit
NOK 34,000
Equity
NOK 513,000
Est. value
NOK 358,000

Financial health · 2025

Liquidity
1.49
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.8%
Good
Equity as a share of total capital

Who owns SELEKTIV MARKEDSFØRING AS?

CAMAH INVEST AS
SELEKTIV MARKEDSFØRING AS
NOK 146,000 rev. · NOK 34,000 profit

SELEKTIV MARKEDSFØRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SELEKTIV MARKEDSFØRING AS

Who owns SELEKTIV MARKEDSFØRING AS?

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

What is the revenue of SELEKTIV MARKEDSFØRING AS?

SELEKTIV MARKEDSFØRING AS had revenue of NOK 146,000 in 2025.

Who is the general manager of SELEKTIV MARKEDSFØRING AS?

Helge Guttorm Hallingby is registered as general manager of SELEKTIV MARKEDSFØRING AS.

Where is SELEKTIV MARKEDSFØRING AS based?

SELEKTIV MARKEDSFØRING AS has its business address in Vegårshei.

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.