biztrac. BETA
COMPANY REGISTER PROFILE
917832811 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

TRIPPEL-M AS

Org. no. 917832811 Limited company (AS) Sandnes Incorporated 2016 Active
Operating profit NOK −59,000
Equity NOK 11.5m
Incorporated 2016
Share capital NOK 30,000

Signals

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

TRIPPEL-M AS is registered as a limited company in Sandnes, Rogaland with organisation number 917832811. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Aksjebesittelse, herunder handel med verdipapirer med deltakelse i andre selskap, samt lånefinansierte investeringer med verdipapirer og valuta. I tillegg skal selskapet drive med kjøp/salg og drift av fast eiendom samt utleie, framleie og salg av kapitalgjenstander/eiendom og løsøre.”.

Key figures · 2025

Operating profit
NOK −59,000
▼ −317 %
Equity
NOK 11.5m
▼ −0 %
Est. value
NOK 18.9m

Financial health · 2025

Liquidity
2.53
Very good
Current assets ÷ current liabilities
Profitability
18.6%
Very good
Return on total assets
Solidity
69.6%
Very good
Equity as a share of total capital

Who owns TRIPPEL-M AS?

TRIPPEL-M AS has 3 registered shareholders:

All shareholders and roles →

Which companies does TRIPPEL-M AS own?

TRIPPEL-M AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TRIPPEL-M AS

Who owns TRIPPEL-M AS?

MEDUSA HOLDING AS is the largest registered owner, with 33.3%.

Who is the general manager of TRIPPEL-M AS?

Maiken Johnsen is registered as general manager of TRIPPEL-M AS.

Where is TRIPPEL-M AS based?

TRIPPEL-M AS has its business address in Sandnes.

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.