BIZTRAC BETA
COMPANY REGISTER PROFILE
975997898 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities of charities which distribute means themselves

JAC O LYNGAAS OG HUSTRUS STIFTELSE

Org. no. 975997898 Foundation (STI) Tønsberg Incorporated 1995 Active
Ownership graph ↗
Operating profit NOK −168,000
Equity NOK 16.0m
Incorporated 1995
Share capital NOK 12.8m

Signals

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

JAC O LYNGAAS OG HUSTRUS STIFTELSE is registered as a foundation in Tønsberg, Vestfold with organisation number 975997898. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 1995. Registered share capital is NOK 12.8m.

Key figures · 2025

Operating profit
NOK −168,000
Equity
NOK 16.0m
Est. value
NOK 16.7m

Financial health · 2025

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

Who owns JAC O LYNGAAS OG HUSTRUS STIFTELSE?

No shareholders are registered for JAC O LYNGAAS OG HUSTRUS STIFTELSE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about JAC O LYNGAAS OG HUSTRUS STIFTELSE

Where is JAC O LYNGAAS OG HUSTRUS STIFTELSE based?

JAC O LYNGAAS OG HUSTRUS STIFTELSE has its business address in Tønsberg.

Property

Business address Storgaten 35, 3126 Tønsberg
Cadastral unit 3905-1002/89/0/0
Building Butikkbygning · 1 unit

2 companies are registered at this address.

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.