BIZTRAC BETA
COMPANY REGISTER PROFILE
920618669 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

RUGDE AS

Org. no. 920618669 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −11,000
Equity NOK 4.3m
Incorporated 2018
Share capital NOK 30,000

Signals

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

RUGDE AS is registered as a limited company in Oslo, Oslo with organisation number 920618669. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i aksjer og andre verdipapirer samt det som står i naturlig forbindelse med dette.”. 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
Equity
NOK 4.3m
Est. value
NOK 4.2m

Financial health · 2025

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

Who owns RUGDE AS?

EVEN LUND
RUGDE AS
NOK 0 rev. · NOK −11,000 profit

RUGDE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RUGDE AS own?

RUGDE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RUGDE AS

Who owns RUGDE AS?

EVEN LUND is the largest registered owner, with 100.0%.

What is the revenue of RUGDE AS?

RUGDE AS had revenue of NOK 0 in 2025.

Who is the general manager of RUGDE AS?

Even Lund is registered as general manager of RUGDE AS.

Where is RUGDE AS based?

RUGDE AS has its business address in Oslo.

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.