biztrac. BETA
COMPANY REGISTER PROFILE
997879872 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other activities of other membership organisations

MIDLANDS CHILDREN HOPE PROJECT.

Org. no. 997879872 Association/club/organisation (FLI) Nesbyen Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 188,000
Operating profit NOK −107,000
Equity NOK 117,000
Incorporated 2012

Signals

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

MIDLANDS CHILDREN HOPE PROJECT. is registered as a association/club/organisation in Nesbyen, Buskerud with organisation number 997879872. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 2012. The most recent filed accounts, for the 2025 financial year, show NOK 188,000 in revenue and NOK −107,000 in operating profit.

Key figures · 2025

Revenue
NOK 188,000
▼ −73 %
Operating profit
NOK −107,000
▲ +58 %
Equity
NOK 117,000
▼ −46 %
Est. value
NOK 190,000

Financial health · 2025

Liquidity
4.92
Very good
Current assets ÷ current liabilities
Profitability
-50.8%
Not satisfactory
Return on total assets
Solidity
79.7%
Very good
Equity as a share of total capital

Who owns MIDLANDS CHILDREN HOPE PROJECT.?

No shareholders are registered for MIDLANDS CHILDREN HOPE PROJECT. in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about MIDLANDS CHILDREN HOPE PROJECT.

What is the revenue of MIDLANDS CHILDREN HOPE PROJECT.?

MIDLANDS CHILDREN HOPE PROJECT. had revenue of NOK 188,000 in 2025.

Who is the general manager of MIDLANDS CHILDREN HOPE PROJECT.?

Lene Tollefsen Rodegård is registered as general manager of MIDLANDS CHILDREN HOPE PROJECT..

Where is MIDLANDS CHILDREN HOPE PROJECT. based?

MIDLANDS CHILDREN HOPE PROJECT. has its business address in Nesbyen.

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.