BIZTRAC BETA
Business and other management consultancy activities

M.ALGRØY AS

Org. no. 925189324 Limited company (AS) Holmestrand Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −79,000
Equity NOK 14.1m
Incorporated 2020
Share capital NOK 34,000

Signals

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

M.ALGRØY AS is registered as a limited company in Holmestrand, Vestfold with organisation number 925189324. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020. Registered share capital is NOK 34,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer, yte konsulenttjenester og alt som herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −79,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −79,000
Equity
NOK 14.1m
Est. value
NOK 10.6m

Financial health · 2025

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

Who owns M.ALGRØY AS?

MARTIN INGE ALGRØY
M.ALGRØY AS
NOK 0 rev. · NOK −79,000 profit

M.ALGRØY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does M.ALGRØY AS own?

M.ALGRØY AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about M.ALGRØY AS

Who owns M.ALGRØY AS?

MARTIN INGE ALGRØY is the largest registered owner, with 100.0%.

What is the revenue of M.ALGRØY AS?

M.ALGRØY AS had revenue of NOK 0 in 2025.

Who is the general manager of M.ALGRØY AS?

Martin Inge Algrøy is registered as general manager of M.ALGRØY AS.

Where is M.ALGRØY AS based?

M.ALGRØY AS has its business address in Hof.

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.