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

BLINGSMOVEGEN 60 AS

Org. no. 928789578 Limited company (AS) Nesbyen Incorporated 2022 Active
Revenue 2025 NOK 3.4m
Operating profit NOK 1.8m
Equity NOK 10.4m
Incorporated 2022
Share capital NOK 11.0m

BLINGSMOVEGEN 60 AS is registered as a limited company in Nesbyen, Buskerud with organisation number 928789578. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 11.0m, divided into 30 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom og som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
▼ −9 %
Operating profit
NOK 1.8m
▼ −13 %
Equity
NOK 10.4m
▼ −11 %
Est. value
NOK 9.9m

Financial health · 2025

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
2.8%
Weak
Return on total assets
Solidity
16.6%
Satisfactory
Equity as a share of total capital

Who owns BLINGSMOVEGEN 60 AS?

BLINGSMOVEGEN 60 AS
NOK 3.4m rev. · NOK 1.8m profit

BLINGSMOVEGEN 60 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLINGSMOVEGEN 60 AS

Who owns BLINGSMOVEGEN 60 AS?

BRINGO SAG & HØVLERI AS is the largest registered owner, with 100.0%.

What is the revenue of BLINGSMOVEGEN 60 AS?

BLINGSMOVEGEN 60 AS had revenue of NOK 3.4m in 2025.

Who is the general manager of BLINGSMOVEGEN 60 AS?

Endre Bringo is registered as general manager of BLINGSMOVEGEN 60 AS.

Where is BLINGSMOVEGEN 60 AS based?

BLINGSMOVEGEN 60 AS has its business address in Nesbyen.

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.