biztrac. BETA
COMPANY REGISTER PROFILE
932752182 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

TRUDVANG TERRASSE B1 BORETTSLAG

Org. no. 932752182 Housing cooperative (BRL) Tønsberg Incorporated 1959 Active
Ownership graph ↗
Revenue 2025 NOK 766,000
Operating profit NOK 147,000
Equity NOK −247,000
Incorporated 1959

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−247k kr).
  • Nylig endring 2026-04-29 Adresseendring registrert 2026-04-29.

TRUDVANG TERRASSE B1 BORETTSLAG is registered as a housing cooperative in Tønsberg, Vestfold with organisation number 932752182. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1959. The company's stated purpose is: “Borettslag”. The most recent filed accounts, for the 2025 financial year, show NOK 766,000 in revenue and NOK 147,000 in operating profit.

Former names: AS TRUDVANG TERRASSE B 1

Key figures · 2025

Revenue
NOK 766,000
▲ +19 %
Operating profit
NOK 147,000
▲ +2819 %
Equity
NOK −247,000
▲ +30 %
Est. value
NOK 328,000

Financial health · 2025

Liquidity
1.53
Good
Current assets ÷ current liabilities
Profitability
25.9%
Very good
Return on total assets
Solidity
-41.2%
Weak
Equity as a share of total capital

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

Who owns TRUDVANG TERRASSE B1 BORETTSLAG?

No shareholders are registered for TRUDVANG TERRASSE B1 BORETTSLAG in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about TRUDVANG TERRASSE B1 BORETTSLAG

What is the revenue of TRUDVANG TERRASSE B1 BORETTSLAG?

TRUDVANG TERRASSE B1 BORETTSLAG had revenue of NOK 766,000 in 2025.

Where is TRUDVANG TERRASSE B1 BORETTSLAG based?

TRUDVANG TERRASSE B1 BORETTSLAG 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.