BIZTRAC BETA
Civil engineering activities

MASSIVTRE KONSULT AS

Org. no. 934522044 Limited company (AS) Frogn Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 613,000
Operating profit NOK 126,000
Equity NOK 165,000
Incorporated 2024
Share capital NOK 30,000

MASSIVTRE KONSULT AS is registered as a limited company in Frogn, Akershus with organisation number 934522044. The business is classified under civil engineering activities (NACE 71.121). 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 byggteknisk konsulentvirksomhet og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 613,000 in revenue and NOK 126,000 in operating profit.

Key figures · 2025

Revenue
NOK 613,000
Operating profit
NOK 126,000
Equity
NOK 165,000
Est. value
NOK 620,000

Financial health · 2025

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

Who owns MASSIVTRE KONSULT AS?

PAVEL NOSEK
MASSIVTRE KONSULT AS
NOK 613,000 rev. · NOK 126,000 profit

MASSIVTRE KONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MASSIVTRE KONSULT AS

Who owns MASSIVTRE KONSULT AS?

PAVEL NOSEK is the largest registered owner, with 100.0%.

What is the revenue of MASSIVTRE KONSULT AS?

MASSIVTRE KONSULT AS had revenue of NOK 613,000 in 2025.

Who is the general manager of MASSIVTRE KONSULT AS?

Pavel Nosek is registered as general manager of MASSIVTRE KONSULT AS.

Where is MASSIVTRE KONSULT AS based?

MASSIVTRE KONSULT AS has its business address in Nordre Frogn.

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.