BIZTRAC BETA
Rental and operating of own or leased real estate

JÆDEREN AS

Org. no. 992060409 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 180,000
Operating profit NOK 78,000
Equity NOK 226.0m
Incorporated 2007
Share capital NOK 630,000

JÆDEREN AS is registered as a limited company in Oslo, Oslo with organisation number 992060409. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 630,000, divided into 6000 shares. The company's stated purpose is: “Eie og investere i aksjer, eiendom og andre selskaper og virksomheter, samt deltakelse av enhver art i andre forretningsforetakende og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 180,000 in revenue and NOK 78,000 in operating profit.

Key figures · 2024

Revenue
NOK 180,000
Operating profit
NOK 78,000
Equity
NOK 226.0m
Est. value
NOK 154.9m

Financial health · 2024

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

Who owns JÆDEREN AS?

PETTER HODNE STEENSLAND
JÆDEREN AS
NOK 180,000 rev. · NOK 78,000 profit

JÆDEREN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JÆDEREN AS own?

JÆDEREN AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about JÆDEREN AS

Who owns JÆDEREN AS?

PETTER HODNE STEENSLAND is the largest registered owner, with 100.0%.

What is the revenue of JÆDEREN AS?

JÆDEREN AS had revenue of NOK 180,000 in 2024.

Who is the general manager of JÆDEREN AS?

Petter Hodne Steensland is registered as general manager of JÆDEREN AS.

Where is JÆDEREN AS based?

JÆDEREN 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.