biztrac. BETA
COMPANY REGISTER PROFILE
870456522 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Contract catering service activities and other food service activities

STIFTELSEN BÅRDSPLASSEN ELDRESENTER

Org. no. 870456522 Foundation (STI) Vestnes Incorporated 1986 Active
Ownership graph ↗
Revenue 2025 NOK 248,000
Operating profit NOK −411,000
Equity NOK 249,000
Incorporated 1986
Share capital NOK 200,000

Signals

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

STIFTELSEN BÅRDSPLASSEN ELDRESENTER is registered as a foundation in Vestnes, Møre og Romsdal with organisation number 870456522. The business is classified under contract catering service activities and other food service activities (NACE 56.220). The company was incorporated in 1986. Registered share capital is NOK 200,000. The most recent filed accounts, for the 2025 financial year, show NOK 248,000 in revenue and NOK −411,000 in operating profit.

Former names: BÅRDSPLASSEN ELDRESENTER

Key figures · 2025

Revenue
NOK 248,000
▲ +43 %
Operating profit
NOK −411,000
▼ −500 %
Equity
NOK 249,000
▼ −61 %
Est. value
NOK 298,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-88.0%
Not satisfactory
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns STIFTELSEN BÅRDSPLASSEN ELDRESENTER?

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

Frequently asked questions about STIFTELSEN BÅRDSPLASSEN ELDRESENTER

What is the revenue of STIFTELSEN BÅRDSPLASSEN ELDRESENTER?

STIFTELSEN BÅRDSPLASSEN ELDRESENTER had revenue of NOK 248,000 in 2025.

Where is STIFTELSEN BÅRDSPLASSEN ELDRESENTER based?

STIFTELSEN BÅRDSPLASSEN ELDRESENTER has its business address in Vikebukt.

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.