BIZTRAC BETA
COMPANY REGISTER PROFILE
911074184 ORG. NO. 2024 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Production of electricity from hydropower

ALBERT COLLETT

Org. no. 911074184 Sole proprietorship (ENK) Namsos Active
Ownership graph ↗
Revenue 2024 NOK 22.8m
Operating profit NOK −1.6m
Equity NOK 48.0m
Employees 30

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,6 mill kr).

ALBERT COLLETT is registered as a sole proprietorship in Namsos, Trøndelag with organisation number 911074184. The business is classified under production of electricity from hydropower (NACE 35.121). The company has 30 registered employees. The most recent filed accounts, for the 2024 financial year, show NOK 22.8m in revenue and NOK −1.6m in operating profit.

Key figures · 2024

Revenue
NOK 22.8m
Operating profit
NOK −1.6m
Equity
NOK 48.0m
Est. value
NOK 38.5m

Financial health · 2024

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

Who owns ALBERT COLLETT?

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

Frequently asked questions about ALBERT COLLETT

What is the revenue of ALBERT COLLETT?

ALBERT COLLETT had revenue of NOK 22.8m in 2024.

Where is ALBERT COLLETT based?

ALBERT COLLETT has its business address in Bangsund.

Property

Business address Fagerholmvegen 2, 7822 Bangsund
Cadastral unit 5007-34/4/0/0
Building Enebolig · 1 unit

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