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

STIFTELSEN RETTFERD

Org. no. 971305991 Foundation (STI) Nordre Land Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 5.0m
Operating profit NOK 115,000
Equity NOK 336,000
Incorporated 1999
Employees 5
Share capital NOK 109,000

STIFTELSEN RETTFERD is registered as a foundation in Nordre Land, Innlandet with organisation number 971305991. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 1999 and has 5 registered employees. Registered share capital is NOK 109,000. The most recent filed accounts, for the 2025 financial year, show NOK 5.0m in revenue and NOK 115,000 in operating profit.

Former names: AKSJON RETTFERD FOR TAPERNE, LANDSFORENINGEN RETTFERD FOR TAPERNE, STIFTELSEN LANDSFORENINGEN RETTFERD FOR TAPERNE, STIFTELSEN RETTFERD FOR TAPERNE

Key figures · 2025

Revenue
NOK 5.0m
▲ +28 %
Operating profit
NOK 115,000
▲ +120 %
Equity
NOK 336,000
▲ +75 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
1.47
Satisfactory
Current assets ÷ current liabilities
Profitability
17.7%
Very good
Return on total assets
Solidity
35.4%
Good
Equity as a share of total capital

Who owns STIFTELSEN RETTFERD?

No shareholders are registered for STIFTELSEN RETTFERD in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STIFTELSEN RETTFERD

What is the revenue of STIFTELSEN RETTFERD?

STIFTELSEN RETTFERD had revenue of NOK 5.0m in 2025.

Who is the general manager of STIFTELSEN RETTFERD?

Tor Bernhard Slaathaug is registered as general manager of STIFTELSEN RETTFERD.

Where is STIFTELSEN RETTFERD based?

STIFTELSEN RETTFERD has its business address in Dokka.

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.