BIZTRAC BETA
Sports and recreation education

BEVEGELSESPRAKSIS AS

Org. no. 834222752 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 157,000
Operating profit NOK 121,000
Equity NOK 120,000
Incorporated 2024
Share capital NOK 30,000

BEVEGELSESPRAKSIS AS is registered as a limited company in Oslo, Oslo with organisation number 834222752. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen undervisning innen sport og idrett og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 157,000 in revenue and NOK 121,000 in operating profit.

Key figures · 2024

Revenue
NOK 157,000
Operating profit
NOK 121,000
Equity
NOK 120,000
Est. value
NOK 497,000

Financial health · 2024

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

Who owns BEVEGELSESPRAKSIS AS?

VEMUND SÆTRE SKULBERG
BEVEGELSESPRAKSIS AS
NOK 157,000 rev. · NOK 121,000 profit

BEVEGELSESPRAKSIS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BEVEGELSESPRAKSIS AS

Who owns BEVEGELSESPRAKSIS AS?

VEMUND SÆTRE SKULBERG is the largest registered owner, with 100.0%.

What is the revenue of BEVEGELSESPRAKSIS AS?

BEVEGELSESPRAKSIS AS had revenue of NOK 157,000 in 2024.

Who is the general manager of BEVEGELSESPRAKSIS AS?

Vemund Sætre Skulberg is registered as general manager of BEVEGELSESPRAKSIS AS.

Where is BEVEGELSESPRAKSIS AS based?

BEVEGELSESPRAKSIS AS has its business address in Oslo.

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.