BIZTRAC BETA
COMPANY REGISTER PROFILE
912502880 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

NRW HOLDING AS

Org. no. 912502880 Limited company (AS) Aure Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −11,000
Equity NOK 1.1m
Incorporated 2013
Share capital NOK 30,000

Signals

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

NRW HOLDING AS is registered as a limited company in Aure, Møre og Romsdal with organisation number 912502880. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, samt virksomhet som naturlig faller inn under dette, som investering i fast eiendom, samt administrasjon og ledelse av andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −11,000
▲ +83 %
Equity
NOK 1.1m
▲ +73 %
Est. value
NOK 2.8m

Financial health · 2025

Liquidity
2.73
Very good
Current assets ÷ current liabilities
Profitability
64.0%
Very good
Return on total assets
Solidity
80.1%
Very good
Equity as a share of total capital

Who owns NRW HOLDING AS?

NRW HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does NRW HOLDING AS own?

NRW HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about NRW HOLDING AS

Who owns NRW HOLDING AS?

GRAZVYDAS RUSECKAS is the largest registered owner, with 33.3%.

What is the revenue of NRW HOLDING AS?

NRW HOLDING AS had revenue of NOK 0 in 2025.

Where is NRW HOLDING AS based?

NRW HOLDING AS has its business address in Tustna.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.