BIZTRAC BETA
Business and other management consultancy activities

PRAXES AS

Org. no. 913153286 Limited company (AS) Frosta Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK −203,000
Equity NOK 115,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−203k kr).

PRAXES AS is registered as a limited company in Frosta, Trøndelag with organisation number 913153286. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Rådgiving, analyser, undervisning og forskning, samt annen virksomhet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK −203,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK −203,000
Equity
NOK 115,000
Est. value
NOK 1.2m

Financial health · 2024

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.8%
Satisfactory
Equity as a share of total capital

Who owns PRAXES AS?

ROGER KLEV
PRAXES AS
NOK 1.3m rev. · NOK −203,000 profit

PRAXES AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PRAXES AS own?

PRAXES AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PRAXES AS

Who owns PRAXES AS?

ROGER KLEV is the largest registered owner, with 100.0%.

What is the revenue of PRAXES AS?

PRAXES AS had revenue of NOK 1.3m in 2025.

Who is the general manager of PRAXES AS?

Roger Klev is registered as general manager of PRAXES AS.

Where is PRAXES AS based?

PRAXES AS has its business address in Frosta.

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.