BIZTRAC BETA
COMPANY REGISTER PROFILE
951228133 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

BRUSTAD ANS

Org. no. 951228133 General partnership (ANS) Nesbyen Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 0
Incorporated 1988

BRUSTAD ANS is registered as a general partnership in Nesbyen, Buskerud with organisation number 951228133. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1988. The company's stated purpose is: “Drive eiendomsutvikling og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 0

Financial health · 2025

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

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

Who owns BRUSTAD ANS?

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

Frequently asked questions about BRUSTAD ANS

What is the revenue of BRUSTAD ANS?

BRUSTAD ANS had revenue of NOK 0 in 2025.

Where is BRUSTAD ANS based?

BRUSTAD ANS has its business address in Nesbyen.

Property

Business address c/o Rukke Eiendom AS Nesmoen 36, 3540 Nesbyen
Cadastral unit 3322-85/8/0/0

7 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.