BIZTRAC BETA
Activities of advertising agencies

RISØR BY AS

Org. no. 915820395 Limited company (AS) Risør Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 142,000
Equity NOK 667,000
Incorporated 2015
Share capital NOK 150,000

Signals

1 flags
  • Nylig endring 2026-02-09 Adresseendring registrert 2026-02-09.

RISØR BY AS is registered as a limited company in Risør, Agder with organisation number 915820395. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2015. Registered share capital is NOK 150,000, divided into 150000 shares. The company's stated purpose is: “Omsetning av tjenester til næringsdrivende i Risør i form av profilering, handelsaktiviteter, sentrumsaktiviteter og kulturaktiviteter. Selskapet vil med dette bidra til å styrke lokale og regionale bedrifters lønnsomhet og verdiskaping.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 142,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 142,000
Equity
NOK 667,000
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns RISØR BY AS?

RISØR KOMMUNE
RISØR BY AS
NOK 1.6m rev. · NOK 142,000 profit

RISØR BY AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does RISØR BY AS own?

RISØR BY AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RISØR BY AS

Who owns RISØR BY AS?

RISØR KOMMUNE is the largest registered owner, with 32.9%.

What is the revenue of RISØR BY AS?

RISØR BY AS had revenue of NOK 1.6m in 2025.

Where is RISØR BY AS based?

RISØR BY AS has its business address in Risør.

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.