BIZTRAC BETA
COMPANY REGISTER PROFILE
988770396 ORG. NO. 2023 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Other activities of other membership organisations

FRIMURERLOGEN I TØNSBERG

Org. no. 988770396 Association/club/organisation (FLI) Tønsberg Incorporated 1926 Active
Ownership graph ↗
Equity NOK 0
Incorporated 1926

FRIMURERLOGEN I TØNSBERG is registered as a association/club/organisation in Tønsberg, Vestfold with organisation number 988770396. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 1926.

Former names: FRIMURERGÅRDEN ST. JOHANNESLOGEN ST. MICHAEL TIL DET LYSENDE KORS

Key figures · 2023

Equity
NOK 0

Financial health · 2023

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FRIMURERLOGEN I TØNSBERG?

No shareholders are registered for FRIMURERLOGEN I TØNSBERG in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does FRIMURERLOGEN I TØNSBERG own?

FRIMURERLOGEN I TØNSBERG holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FRIMURERLOGEN I TØNSBERG

Where is FRIMURERLOGEN I TØNSBERG based?

FRIMURERLOGEN I TØNSBERG has its business address in Tønsberg.

Property

Business address Kammegaten 4, 3110 Tønsberg
Cadastral unit 3905-1002/261/0/0
Building Restaurantbygning, kafébygning · 1 unit

3 companies are registered at this address.

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.