BIZTRAC BETA
Other technical consultancy

GRANLI TEKNISKE AS

Org. no. 935097622 Limited company (AS) Larvik Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 485,000
Operating profit NOK 23,000
Equity NOK 48,000
Incorporated 2025
Share capital NOK 30,000

GRANLI TEKNISKE AS is registered as a limited company in Larvik, Vestfold with organisation number 935097622. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Teknisk support og service på drivstoffanlegg, herunder ny montering av drivstoffanlegg, samt vaktmestertjenester og andre tjenester relatert til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 485,000 in revenue and NOK 23,000 in operating profit.

Key figures · 2025

Revenue
NOK 485,000
Operating profit
NOK 23,000
Equity
NOK 48,000
Est. value
NOK 139,000

Financial health · 2025

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

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

Who owns GRANLI TEKNISKE AS?

GRANLI INVESTERING AS
GRANLI TEKNISKE AS
NOK 485,000 rev. · NOK 23,000 profit

GRANLI TEKNISKE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about GRANLI TEKNISKE AS

Who owns GRANLI TEKNISKE AS?

GRANLI INVESTERING AS is the largest registered owner, with 50.0%.

What is the revenue of GRANLI TEKNISKE AS?

GRANLI TEKNISKE AS had revenue of NOK 485,000 in 2025.

Who is the general manager of GRANLI TEKNISKE AS?

Daniel Stefan Granli is registered as general manager of GRANLI TEKNISKE AS.

Where is GRANLI TEKNISKE AS based?

GRANLI TEKNISKE AS has its business address in Tjodalyng.

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.