BIZTRAC BETA
COMPANY REGISTER PROFILE
917863172 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

A. RUNDGREN HOLDING AS

Org. no. 917863172 Limited company (AS) Bergen Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 884,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).

A. RUNDGREN HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 917863172. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å eie aksjer, samt investeringer i virksomheter av enhver art.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 884,000
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns A. RUNDGREN HOLDING AS?

ARILD RUNDGREN
A. RUNDGREN HOLDING AS
NOK 0 rev. · NOK −13,000 profit

A. RUNDGREN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about A. RUNDGREN HOLDING AS

Who owns A. RUNDGREN HOLDING AS?

ARILD RUNDGREN is the largest registered owner, with 100.0%.

What is the revenue of A. RUNDGREN HOLDING AS?

A. RUNDGREN HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of A. RUNDGREN HOLDING AS?

Arild Rundgren is registered as general manager of A. RUNDGREN HOLDING AS.

Where is A. RUNDGREN HOLDING AS based?

A. RUNDGREN HOLDING AS has its business address in Bergen.

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.