biztrac. BETA
COMPANY REGISTER PROFILE
923025472 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Sports and recreation education

PAULSBYEN GYM ELVERUM AS

Org. no. 923025472 Limited company (AS) Elverum Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 1.5m
Equity NOK 1.7m
Incorporated 2019
Share capital NOK 30,000

PAULSBYEN GYM ELVERUM AS is registered as a limited company in Elverum, Innlandet with organisation number 923025472. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drift av treningssenter”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 1.5m in operating profit.

Former names: PAULSBYENS GYM AS

Key figures · 2025

Revenue
NOK 3.2m
▼ −14 %
Operating profit
NOK 1.5m
▼ −14 %
Equity
NOK 1.7m
▲ +12 %
Est. value
NOK 6.6m

Financial health · 2025

Liquidity
3.16
Very good
Current assets ÷ current liabilities
Profitability
49.6%
Very good
Return on total assets
Solidity
83.7%
Very good
Equity as a share of total capital

Who owns PAULSBYEN GYM ELVERUM AS?

PAULSBYEN GYM ELVERUM AS
NOK 3.2m rev. · NOK 1.5m profit

PAULSBYEN GYM ELVERUM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PAULSBYEN GYM ELVERUM AS

Who owns PAULSBYEN GYM ELVERUM AS?

PAULSBYEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of PAULSBYEN GYM ELVERUM AS?

PAULSBYEN GYM ELVERUM AS had revenue of NOK 3.2m in 2025.

Who is the general manager of PAULSBYEN GYM ELVERUM AS?

Robert Paulsbyen is registered as general manager of PAULSBYEN GYM ELVERUM AS.

Where is PAULSBYEN GYM ELVERUM AS based?

PAULSBYEN GYM ELVERUM AS has its business address in Elverum.

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.