biztrac. BETA
COMPANY REGISTER PROFILE
941428940 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

BLØ BYGG Per Inge Blø & Co

Org. no. 941428940 General partnership with shared liability (DA) Molde Incorporated 1984 Active
Ownership graph ↗
Revenue 2025 NOK 120,000
Operating profit NOK −49,000
Equity NOK 1.1m
Incorporated 1984

Signals

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

BLØ BYGG Per Inge Blø & Co is registered as a general partnership with shared liability in Molde, Møre og Romsdal with organisation number 941428940. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1984. The company's stated purpose is: “Byggevirksomhet og handel.”. The most recent filed accounts, for the 2025 financial year, show NOK 120,000 in revenue and NOK −49,000 in operating profit.

Key figures · 2025

Revenue
NOK 120,000
▲ +0 %
Operating profit
NOK −49,000
▼ −2375 %
Equity
NOK 1.1m
▼ −15 %
Est. value
NOK 953,000

Financial health · 2025

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

Who owns BLØ BYGG Per Inge Blø & Co?

No shareholders are registered for BLØ BYGG Per Inge Blø & Co in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BLØ BYGG Per Inge Blø & Co

What is the revenue of BLØ BYGG Per Inge Blø & Co?

BLØ BYGG Per Inge Blø & Co had revenue of NOK 120,000 in 2025.

Who is the general manager of BLØ BYGG Per Inge Blø & Co?

Per Inge Blø is registered as general manager of BLØ BYGG Per Inge Blø & Co.

Where is BLØ BYGG Per Inge Blø & Co based?

BLØ BYGG Per Inge Blø & Co has its business address in Midsund.

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.