BIZTRAC BETA
Graphic design and visual communication activities

ATELIER ROGNE AS

Org. no. 934373448 Limited company (AS) Hamar Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 94,000
Operating profit NOK 82,000
Equity NOK 92,000
Incorporated 2024
Share capital NOK 30,000

ATELIER ROGNE AS is registered as a limited company in Hamar, Innlandet with organisation number 934373448. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Grafisk design, rådgivning, illustrasjon, kunstnerisk aktivitet, medieproduksjon og annet som naturlig faller sammen med dette, herunder å delta i selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 94,000 in revenue and NOK 82,000 in operating profit.

Key figures · 2025

Revenue
NOK 94,000
Operating profit
NOK 82,000
Equity
NOK 92,000
Est. value
NOK 322,000

Financial health · 2025

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

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

Who owns ATELIER ROGNE AS?

JØRGEN ANDREAS ROGNE
ATELIER ROGNE AS
NOK 94,000 rev. · NOK 82,000 profit

ATELIER ROGNE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ATELIER ROGNE AS

Who owns ATELIER ROGNE AS?

JØRGEN ANDREAS ROGNE is the largest registered owner, with 100.0%.

What is the revenue of ATELIER ROGNE AS?

ATELIER ROGNE AS had revenue of NOK 94,000 in 2025.

Where is ATELIER ROGNE AS based?

ATELIER ROGNE AS has its business address in Hamar.

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.