BIZTRAC BETA
Painting and glazing

A. ROSENBORG AS

Org. no. 912835731 Limited company (AS) Ringerike Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 328,000
Equity NOK 3.6m
Incorporated 2013
Share capital NOK 30,000

A. ROSENBORG AS is registered as a limited company in Ringerike, Buskerud with organisation number 912835731. The business is classified under painting and glazing (NACE 43.340). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg og import av biler og juletrær, håndverksvirksomhet, maling m.v., konsulentvirksomhet samt annen virksomhet som naturlig hører sammen med dette, herunder å delta i andre 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 2.1m in revenue and NOK 328,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 328,000
Equity
NOK 3.6m
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns A. ROSENBORG AS?

ALIKS ROSENBORG
A. ROSENBORG AS
NOK 2.1m rev. · NOK 328,000 profit

A. ROSENBORG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about A. ROSENBORG AS

Who owns A. ROSENBORG AS?

ALIKS ROSENBORG is the largest registered owner, with 100.0%.

What is the revenue of A. ROSENBORG AS?

A. ROSENBORG AS had revenue of NOK 2.1m in 2025.

Who is the general manager of A. ROSENBORG AS?

Aliks Rosenborg is registered as general manager of A. ROSENBORG AS.

Where is A. ROSENBORG AS based?

A. ROSENBORG AS has its business address in Hønefoss.

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.