BIZTRAC BETA
Rental and operating of own or leased real estate

AS SVERRESGT 9

Org. no. 830887482 Limited company (AS) Porsgrunn Incorporated 1934 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 210,000
Equity NOK 1.6m
Incorporated 1934
Share capital NOK 369,000

AS SVERRESGT 9 is registered as a limited company in Porsgrunn, Telemark with organisation number 830887482. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1934. Registered share capital is NOK 369,000, divided into 7376 shares. The company's stated purpose is: “Eie og drive Sverresg 9, Porsgrunn, for å skaffe Odd Fellow Ordenen høvelige lokaler.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 210,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 210,000
Equity
NOK 1.6m
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns AS SVERRESGT 9?

ODD FELLOW LOGE NR. 17 DAG
AS SVERRESGT 9
NOK 2.4m rev. · NOK 210,000 profit

AS SVERRESGT 9 has 20+ registered shareholders:

All shareholders and roles →

Which companies does AS SVERRESGT 9 own?

AS SVERRESGT 9 holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AS SVERRESGT 9

Who owns AS SVERRESGT 9?

ODD FELLOW LOGE NR. 17 DAG is the largest registered owner, with 38.3%.

What is the revenue of AS SVERRESGT 9?

AS SVERRESGT 9 had revenue of NOK 2.4m in 2025.

Who is the general manager of AS SVERRESGT 9?

Ronald Cato Haaland is registered as general manager of AS SVERRESGT 9.

Where is AS SVERRESGT 9 based?

AS SVERRESGT 9 has its business address in Porsgrunn.

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.