BIZTRAC BETA
Activities of advertising agencies

REKLAMEDAMA AS

Org. no. 935647738 Limited company (AS) Nordreisa Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 272,000
Operating profit NOK 51,000
Equity NOK 65,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-17 Adresseendring registrert 2026-06-17.

REKLAMEDAMA AS is registered as a limited company in Nordreisa, Troms with organisation number 935647738. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Reklamevirksomhet, konsulenttjenester, kjøp og salg av produkter og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 272,000 in revenue and NOK 51,000 in operating profit.

Key figures · 2025

Revenue
NOK 272,000
Operating profit
NOK 51,000
Equity
NOK 65,000
Est. value
NOK 255,000

Financial health · 2025

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

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

Who owns REKLAMEDAMA AS?

MATILDE PERSEN
REKLAMEDAMA AS
NOK 272,000 rev. · NOK 51,000 profit

REKLAMEDAMA AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about REKLAMEDAMA AS

Who owns REKLAMEDAMA AS?

MATILDE PERSEN is the largest registered owner, with 50.0%.

What is the revenue of REKLAMEDAMA AS?

REKLAMEDAMA AS had revenue of NOK 272,000 in 2025.

Who is the general manager of REKLAMEDAMA AS?

Matilde Persen is registered as general manager of REKLAMEDAMA AS.

Where is REKLAMEDAMA AS based?

REKLAMEDAMA AS has its business address in Sørkjosen.

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.