BIZTRAC BETA
COMPANY REGISTER PROFILE
915636926 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other activities of other membership organisations

MEMOAR

Org. no. 915636926 Association/club/organisation (FLI) Bergen Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 515,000
Equity NOK 747,000
Incorporated 2015

Signals

1 flags
  • Nylig endring 2026-04-17 Adresseendring registrert 2026-04-17.

MEMOAR is registered as a association/club/organisation in Bergen, Vestland with organisation number 915636926. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 2015. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 515,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 515,000
Equity
NOK 747,000
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns MEMOAR?

No shareholders are registered for MEMOAR in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about MEMOAR

What is the revenue of MEMOAR?

MEMOAR had revenue of NOK 3.3m in 2025.

Who is the general manager of MEMOAR?

Sebastian Kvamsdal Kaasa is registered as general manager of MEMOAR.

Where is MEMOAR based?

MEMOAR has its business address in Bergen.

Property

Business address Thormøhlens gate 30, 5006 Bergen
Cadastral unit 4601-164/349/0/0

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.