BIZTRAC BETA
Construction of residential and non-residential buildings

RUS13 HOLDING AS

Org. no. 919161051 Limited company (AS) Nittedal Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −19,000
Equity NOK 751,000
Incorporated 2017
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−19k kr).

RUS13 HOLDING AS is registered as a limited company in Nittedal, Akershus with organisation number 919161051. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, drift og utleie av fast eiendom, samt annen virksomhet som står i nær tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −19,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −19,000
Equity
NOK 751,000
Est. value
NOK 770,000

Financial health · 2024

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

Who owns RUS13 HOLDING AS?

KFG HOLDING AS
RUS13 HOLDING AS
NOK 0 rev. · NOK −19,000 profit

RUS13 HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RUS13 HOLDING AS own?

RUS13 HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RUS13 HOLDING AS

Who owns RUS13 HOLDING AS?

KFG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RUS13 HOLDING AS?

RUS13 HOLDING AS had revenue of NOK 0 in 2024.

Where is RUS13 HOLDING AS based?

RUS13 HOLDING AS has its business address in Nittedal.

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.