BIZTRAC BETA
Buying and selling of own real estate

GRANÅSVEIEN 3 AS

Org. no. 988270695 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 24,000
Operating profit NOK −312,000
Equity NOK 5.5m
Incorporated 2005
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−312k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GRANÅSVEIEN 3 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 988270695. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive virksomhet innen kjøp og salg av fast eiendom, herunder deltakelse i andre selskaper samt hva som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 24,000 in revenue and NOK −312,000 in operating profit.

Key figures · 2024

Revenue
NOK 24,000
Operating profit
NOK −312,000
Equity
NOK 5.5m
Est. value
NOK 5.0m

Financial health · 2024

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

Who owns GRANÅSVEIEN 3 AS?

GRANÅSVEIEN 1 AS
GRANÅSVEIEN 3 AS
NOK 24,000 rev. · NOK −312,000 profit

GRANÅSVEIEN 3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRANÅSVEIEN 3 AS

Who owns GRANÅSVEIEN 3 AS?

GRANÅSVEIEN 1 AS is the largest registered owner, with 100.0%.

What is the revenue of GRANÅSVEIEN 3 AS?

GRANÅSVEIEN 3 AS had revenue of NOK 24,000 in 2024.

Where is GRANÅSVEIEN 3 AS based?

GRANÅSVEIEN 3 AS has its business address in Trondheim.

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.