BIZTRAC BETA
General cleaning of buildings

NESSE RENHOLD & VINDUSPUSS AS

Org. no. 917262322 Limited company (AS) Bergen Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 179,000
Equity NOK 662,000
Incorporated 2016
Share capital NOK 30,000

NESSE RENHOLD & VINDUSPUSS AS is registered as a limited company in Bergen, Vestland with organisation number 917262322. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Alt innen renhold/vaktmestertjeneste. Maling-plenklipping-gartner-snørydding. Express budtjeneste til sjøs, med Vestlandet som prioritering. Levering av smågods m.m. Vaktmestertjenester i hytter og lignende som har brygge man kan legge til.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 179,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 179,000
Equity
NOK 662,000
Est. value
NOK 927,000

Financial health · 2025

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

Who owns NESSE RENHOLD & VINDUSPUSS AS?

PÅL NESSE
NESSE RENHOLD & VINDUSPUSS AS
NOK 1.1m rev. · NOK 179,000 profit

NESSE RENHOLD & VINDUSPUSS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NESSE RENHOLD & VINDUSPUSS AS

Who owns NESSE RENHOLD & VINDUSPUSS AS?

PÅL NESSE is the largest registered owner, with 100.0%.

What is the revenue of NESSE RENHOLD & VINDUSPUSS AS?

NESSE RENHOLD & VINDUSPUSS AS had revenue of NOK 1.1m in 2025.

Where is NESSE RENHOLD & VINDUSPUSS AS based?

NESSE RENHOLD & VINDUSPUSS AS has its business address in Bergen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.