BIZTRAC BETA
General cleaning of buildings

VELEMOEN AS

Org. no. 828689452 Limited company (AS) Vinje Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 196,000
Equity NOK 171,000
Incorporated 2022
Employees 10
Share capital NOK 30,000

VELEMOEN AS is registered as a limited company in Vinje, Telemark with organisation number 828689452. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2022 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drift av vaskebyrå med reinhaldstjenester og vaktmestertjenester, samt serveringsvirksomhet med drift av kiosk og kafe og det som naturleg høyrer saman med dette, samt investering i aksjar og andelar i andre selskap som har økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 196,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 196,000
Equity
NOK 171,000
Est. value
NOK 814,000

Financial health · 2025

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

Who owns VELEMOEN AS?

MARIANNE CHRISTENSEN MOEN
VELEMOEN AS
NOK 2.8m rev. · NOK 196,000 profit

VELEMOEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VELEMOEN AS

Who owns VELEMOEN AS?

MARIANNE CHRISTENSEN MOEN is the largest registered owner, with 100.0%.

What is the revenue of VELEMOEN AS?

VELEMOEN AS had revenue of NOK 2.8m in 2025.

Who is the general manager of VELEMOEN AS?

Marianne Christensen Moen is registered as general manager of VELEMOEN AS.

Where is VELEMOEN AS based?

VELEMOEN AS has its business address in Edland.

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.