BIZTRAC BETA
Rental and operating of own or leased real estate

MEMMIS AS

Org. no. 999256309 Limited company (AS) Trondheim Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 356,000
Operating profit NOK −85,000
Equity NOK 4.3m
Incorporated 2012
Share capital NOK 51,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−85k kr).

MEMMIS AS is registered as a limited company in Trondheim, Trøndelag with organisation number 999256309. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 51,000, divided into 51 shares. The company's stated purpose is: “Investering i fast eiendom, direkte og indirekte ved å investere i andre selskap, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 356,000 in revenue and NOK −85,000 in operating profit.

Key figures · 2024

Revenue
NOK 356,000
Operating profit
NOK −85,000
Equity
NOK 4.3m
Est. value
NOK 3.5m

Financial health · 2024

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

Who owns MEMMIS AS?

TINA KLAUSEN
MEMMIS AS
NOK 356,000 rev. · NOK −85,000 profit

MEMMIS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MEMMIS AS own?

MEMMIS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MEMMIS AS

Who owns MEMMIS AS?

TINA KLAUSEN is the largest registered owner, with 76.5%.

What is the revenue of MEMMIS AS?

MEMMIS AS had revenue of NOK 356,000 in 2024.

Where is MEMMIS AS based?

MEMMIS AS has its business address in Tiller.

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.