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

SAMEIET VEIMESTER KROGHSGATE 2 B

Org. no. 990038228 Condominium flat owner (ESEK) Trondheim Incorporated 2006 Active
Revenue 2025 NOK 618,000
Operating profit NOK −73,000
Equity NOK 410,000
Incorporated 2006

Signals

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

SAMEIET VEIMESTER KROGHSGATE 2 B is registered as a condominium flat owner in Trondheim, Trøndelag with organisation number 990038228. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2006. The company's stated purpose is: “Ivareta sameiernes felles interesser som sameiere. Disse vedtektene regulerer forholdet mellom de enkelte sameiere og foreskriver dirft og administrasjon av eiendommen, samt sameiets forhold til naboeiendommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 618,000 in revenue and NOK −73,000 in operating profit.

Key figures · 2025

Revenue
NOK 618,000
▼ −11 %
Operating profit
NOK −73,000
▼ −190 %
Equity
NOK 410,000
▼ −13 %
Est. value
NOK 322,000

Financial health · 2025

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

Who owns SAMEIET VEIMESTER KROGHSGATE 2 B?

No shareholders are registered for SAMEIET VEIMESTER KROGHSGATE 2 B in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SAMEIET VEIMESTER KROGHSGATE 2 B

What is the revenue of SAMEIET VEIMESTER KROGHSGATE 2 B?

SAMEIET VEIMESTER KROGHSGATE 2 B had revenue of NOK 618,000 in 2025.

Where is SAMEIET VEIMESTER KROGHSGATE 2 B based?

SAMEIET VEIMESTER KROGHSGATE 2 B has its business address in Trondheim.

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.