biztrac. BETA
COMPANY REGISTER PROFILE
920382037 ORG. NO. 2018 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

EIERSEKSJONSSAMEIET TØNSBERG GRESSBANE

Org. no. 920382037 Condominium flat owner (ESEK) Tønsberg Incorporated 2003 Active
Ownership graph ↗
Revenue 2018 NOK 631,000
Operating profit NOK −344
Equity NOK −328
Incorporated 2003

Signals

2 flags
  • Negativ egenkapital 2018 Bokført egenkapital er negativ (−328 kr).
  • Driftsunderskudd 2018 Siste driftsresultat er negativt (−344 kr).

EIERSEKSJONSSAMEIET TØNSBERG GRESSBANE is registered as a condominium flat owner in Tønsberg, Vestfold with organisation number 920382037. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2003. The company's stated purpose is: “Eierseksjonssameie”. The most recent filed accounts, for the 2018 financial year, show NOK 631,000 in revenue and NOK −344 in operating profit.

Key figures · 2018

Revenue
NOK 631,000
Operating profit
NOK −344
Equity
NOK −328

Financial health · 2018

Liquidity
1.00
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-0.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns EIERSEKSJONSSAMEIET TØNSBERG GRESSBANE?

No shareholders are registered for EIERSEKSJONSSAMEIET TØNSBERG GRESSBANE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about EIERSEKSJONSSAMEIET TØNSBERG GRESSBANE

What is the revenue of EIERSEKSJONSSAMEIET TØNSBERG GRESSBANE?

EIERSEKSJONSSAMEIET TØNSBERG GRESSBANE had revenue of NOK 631,000 in 2018.

Where is EIERSEKSJONSSAMEIET TØNSBERG GRESSBANE based?

EIERSEKSJONSSAMEIET TØNSBERG GRESSBANE has its business address in Tønsberg.

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.