BIZTRAC BETA
COMPANY REGISTER PROFILE
877151042 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Other activities of other membership organisations

STIFTELSEN FAGFORBUNDET HORTEN

Org. no. 877151042 Foundation (STI) Horten Incorporated 1990 Active
Ownership graph ↗
Operating profit NOK −75,000
Equity NOK 2.9m
Incorporated 1990
Share capital NOK 2.5m

Signals

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

STIFTELSEN FAGFORBUNDET HORTEN is registered as a foundation in Horten, Vestfold with organisation number 877151042. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 1990. Registered share capital is NOK 2.5m.

Former names: BORRE KOMMUNALE FORENING AVD 128

Key figures · 2025

Operating profit
NOK −75,000
Equity
NOK 2.9m
Est. value
NOK 3.9m

Financial health · 2025

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

Who owns STIFTELSEN FAGFORBUNDET HORTEN?

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

Frequently asked questions about STIFTELSEN FAGFORBUNDET HORTEN

Where is STIFTELSEN FAGFORBUNDET HORTEN based?

STIFTELSEN FAGFORBUNDET HORTEN has its business address in Horten.

Property

Business address c/o Eddie Solberg Storgata 1A, 3181 Horten
Cadastral unit 3901-129/205/0/0
Building Stort frittliggende boligbygg på 3 og 4 etg · 42 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.