BIZTRAC BETA
COMPANY REGISTER PROFILE
930629316 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

GRINDEN INVEST AS

Org. no. 930629316 Limited company (AS) Larvik Incorporated 2022 Active
Ownership graph ↗
Equity NOK 254,000
Incorporated 2022
Share capital NOK 30,000

GRINDEN INVEST AS is registered as a limited company in Larvik, Vestfold with organisation number 930629316. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer, andeler og andre finansobjekter samt investering, utvikling og drift av fast eiendom samt hertil hørende virksomhet.”.

Key figures · 2025

Equity
NOK 254,000
▲ +0 %
Est. value
NOK 299,000

Financial health · 2025

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

Who owns GRINDEN INVEST AS?

GRINDEN INVEST AS

GRINDEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GRINDEN INVEST AS own?

GRINDEN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GRINDEN INVEST AS

Who owns GRINDEN INVEST AS?

TOMMY GRINDEN is the largest registered owner, with 100.0%.

Where is GRINDEN INVEST AS based?

GRINDEN INVEST AS has its business address in Larvik.

Property

Business address Lyngveien 19, 3260 Larvik
Cadastral unit 3909-1001/125/0/0
Building Enebolig · 1 unit

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