biztrac. BETA
COMPANY REGISTER PROFILE
927838443 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

FKR AS

Org. no. 927838443 Limited company (AS) Trondheim Incorporated 2021 Active
Revenue 2025 NOK 0
Operating profit NOK −120,000
Equity NOK −1.6m
Incorporated 2021
Share capital NOK 130,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,6 mill kr).

FKR AS is registered as a limited company in Trondheim, Trøndelag with organisation number 927838443. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2021. Registered share capital is NOK 130,000, divided into 130000 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −120,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −120,000
▼ −7 %
Equity
NOK −1.6m
▼ −44 %

Financial health · 2025

Liquidity
25.01
Very good
Current assets ÷ current liabilities
Profitability
-0.0%
Not satisfactory
Return on total assets
Solidity
-26.6%
Weak
Equity as a share of total capital

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

Who owns FKR AS?

FKR AS
NOK 0 rev. · NOK −120,000 profit

FKR AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FKR AS own?

FKR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FKR AS

Who owns FKR AS?

DAFI HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of FKR AS?

FKR AS had revenue of NOK 0 in 2025.

Who is the general manager of FKR AS?

Bjørnar Klein Reinertsen is registered as general manager of FKR AS.

Where is FKR AS based?

FKR AS has its business address in Ranheim.

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.