BIZTRAC BETA
Buying and selling of own real estate

ØYSTEIN JOHNRUD AS

Org. no. 936715036 Limited company (AS) Drammen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 22,000
Operating profit NOK 12,000
Equity NOK 39,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-11-30.

ØYSTEIN JOHNRUD AS is registered as a limited company in Drammen, Buskerud with organisation number 936715036. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, utvikling, forvaltning og utleie av fast eiendom. Vedlikehold, drift og oppgradering av eiendom, samt investering i verdipapirer og annen virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 22,000 in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 22,000
Operating profit
NOK 12,000
Equity
NOK 39,000
Est. value
NOK 57,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ØYSTEIN JOHNRUD AS?

ØYSTEIN KLEVEN JOHNRUD
ØYSTEIN JOHNRUD AS
NOK 22,000 rev. · NOK 12,000 profit

ØYSTEIN JOHNRUD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØYSTEIN JOHNRUD AS

Who owns ØYSTEIN JOHNRUD AS?

ØYSTEIN KLEVEN JOHNRUD is the largest registered owner, with 100.0%.

What is the revenue of ØYSTEIN JOHNRUD AS?

ØYSTEIN JOHNRUD AS had revenue of NOK 22,000 in 2025.

Where is ØYSTEIN JOHNRUD AS based?

ØYSTEIN JOHNRUD AS has its business address in Drammen.

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.