BIZTRAC BETA
Rental and operating of own or leased real estate

PARTYMAN AS

Org. no. 841150732 Limited company (AS) Vefsn Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 7.4m
Operating profit NOK 3.6m
Equity NOK 12.4m
Incorporated 1986
Share capital NOK 150,000

PARTYMAN AS is registered as a limited company in Vefsn, Nordland with organisation number 841150732. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1986. Registered share capital is NOK 150,000, divided into 1200 shares. The company's stated purpose is: “Utleie av eiendom og driftsløsøre og annen utleie som naturlig tilhører denne virksomhet. Selskapet vil også delta i aksjetegning i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.4m in revenue and NOK 3.6m in operating profit.

Key figures · 2024

Revenue
NOK 7.4m
Operating profit
NOK 3.6m
Equity
NOK 12.4m
Est. value
NOK 16.3m

Financial health · 2024

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

Who owns PARTYMAN AS?

MARTINE FJELLHEIM INVEST AS
PARTYMAN AS
NOK 7.4m rev. · NOK 3.6m profit

PARTYMAN AS has 3 registered shareholders:

All shareholders and roles →

Which companies does PARTYMAN AS own?

PARTYMAN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PARTYMAN AS

Who owns PARTYMAN AS?

MARTINE FJELLHEIM INVEST AS is the largest registered owner, with 33.3%.

What is the revenue of PARTYMAN AS?

PARTYMAN AS had revenue of NOK 7.4m in 2024.

Who is the general manager of PARTYMAN AS?

Roar Arvid Abelsen is registered as general manager of PARTYMAN AS.

Where is PARTYMAN AS based?

PARTYMAN AS has its business address in Mosjøen.

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.