biztrac. BETA
COMPANY REGISTER PROFILE
924024046 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

KIRDERF AS

Org. no. 924024046 Limited company (AS) Tønsberg Incorporated 2019 Active
Revenue 2025 NOK 0
Operating profit NOK −31,000
Equity NOK 161.0m
Incorporated 2019
Share capital NOK 30,000

Signals

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

KIRDERF AS is registered as a limited company in Tønsberg, Vestfold with organisation number 924024046. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1200 shares. The company's stated purpose is: “Investeringer i drift av fast eiendom, investeringer i aksjer og selskapsandeler samt handel og hva som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −31,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −31,000
▲ +50 %
Equity
NOK 161.0m
▼ −0 %
Est. value
NOK 143.7m

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
5.2%
Weak
Return on total assets
Solidity
94.6%
Very good
Equity as a share of total capital

Who owns KIRDERF AS?

KIRDERF AS
NOK 0 rev. · NOK −31,000 profit

KIRDERF AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KIRDERF AS own?

KIRDERF AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KIRDERF AS

Who owns KIRDERF AS?

Fredrik Røed is the largest registered owner, with 100.0%.

What is the revenue of KIRDERF AS?

KIRDERF AS had revenue of NOK 0 in 2025.

Where is KIRDERF AS based?

KIRDERF AS has its business address in Tønsberg.

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

Report a problem

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