BIZTRAC BETA
COMPANY REGISTER PROFILE
934921313 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Plumbing installation

GRANBO AS

Org. no. 934921313 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

GRANBO AS is registered as a limited company in Trondheim, Trøndelag with organisation number 934921313. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Å drive med håndtverkstjenester og annet som står i forbindelse med dette.”.

Former names: AFAS 240125-11 AS

Key figures · 2025

Operating profit
NOK −7,000
Equity
NOK 24,000
Est. value
NOK 24,000

Financial health · 2025

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

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

Who owns GRANBO AS?

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

Frequently asked questions about GRANBO AS

Where is GRANBO AS based?

GRANBO AS has its business address in Trondheim.

Property

Business address Vegmesterstien 8A, 7022 Trondheim
Cadastral unit 5001-97/509/0/0
Building Enebolig m/hybel/sokkelleil. · 2 units

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