BIZTRAC BETA
COMPANY REGISTER PROFILE
917984069 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

SIR GRAM AS

Org. no. 917984069 Limited company (AS) Tromsø Incorporated 2016 Active
Ownership graph ↗
Equity NOK 205,000
Incorporated 2016
Share capital NOK 860,000

SIR GRAM AS is registered as a limited company in Tromsø, Troms with organisation number 917984069. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2016. Registered share capital is NOK 860,000, divided into 860 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom og andre driftsmidler, filmproduksjon, konsulenttjenester tilknyttet folkehelsearbeid, E-helse, medisin, kultur og historie, samt deltakelse i andre selskaper.”.

Key figures · 2025

Equity
NOK 205,000
Est. value
NOK 187,000

Financial health · 2025

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

Who owns SIR GRAM AS?

SIR GRAM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SIR GRAM AS

Who owns SIR GRAM AS?

INGER TORHILD GRAM is the largest registered owner, with 50.0%.

Who is the general manager of SIR GRAM AS?

Sigbjørn Rønbeck is registered as general manager of SIR GRAM AS.

Where is SIR GRAM AS based?

SIR GRAM AS has its business address in Tromsø.

Property

Business address Isbakken 2A, 9013 Tromsø
Cadastral unit 5501-118/971/0/0

5 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.