biztrac. BETA
COMPANY REGISTER PROFILE
871431922 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

HOFAGENT DANCKERT D KROHNS STIFTELSE

Org. no. 871431922 Foundation (STI) Bergen Incorporated 1970 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 1.3m
Equity NOK 8.4m
Incorporated 1970
Share capital NOK 832,000

Signals

1 flags
  • Nylig endring 2026-10-05 Adresseendring registrert 2026-10-05.

HOFAGENT DANCKERT D KROHNS STIFTELSE is registered as a foundation in Bergen, Vestland with organisation number 871431922. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 1970. Registered share capital is NOK 832,000. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 1.3m in operating profit.

Former names: KROHNS D STIFTELSE V/ FRØYDIS HOVE, DANCKERT KROHNS STIFTELSE, HOFAGENT DANCKERT KROHNS STIFTELSE

Key figures · 2025

Revenue
NOK 3.0m
▲ +41 %
Operating profit
NOK 1.3m
▲ +240 %
Equity
NOK 8.4m
▲ +8 %
Est. value
NOK 7.6m

Financial health · 2025

Liquidity
7.00
Very good
Current assets ÷ current liabilities
Profitability
10.1%
Good
Return on total assets
Solidity
54.8%
Very good
Equity as a share of total capital

Who owns HOFAGENT DANCKERT D KROHNS STIFTELSE?

No shareholders are registered for HOFAGENT DANCKERT D KROHNS STIFTELSE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about HOFAGENT DANCKERT D KROHNS STIFTELSE

What is the revenue of HOFAGENT DANCKERT D KROHNS STIFTELSE?

HOFAGENT DANCKERT D KROHNS STIFTELSE had revenue of NOK 3.0m in 2025.

Where is HOFAGENT DANCKERT D KROHNS STIFTELSE based?

HOFAGENT DANCKERT D KROHNS STIFTELSE has its business address in Bergen.

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.