BIZTRAC BETA
Technical testing and analysis

GRINDRUD RØRINSPEKSJON AS

Org. no. 915518990 Limited company (AS) Nome Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 14,000
Equity NOK 544,000
Incorporated 2015
Share capital NOK 100,000

GRINDRUD RØRINSPEKSJON AS is registered as a limited company in Nome, Telemark with organisation number 915518990. The business is classified under technical testing and analysis (NACE 71.200). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drive levering av varer og tjenester innen VA-området og det som naturlig hører inn under dette. Selskapet kan også delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 14,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 14,000
Equity
NOK 544,000
Est. value
NOK 359,000

Financial health · 2025

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

Who owns GRINDRUD RØRINSPEKSJON AS?

KNUT OLAV GRINDRUD
GRINDRUD RØRINSPEKSJON AS
NOK 1.4m rev. · NOK 14,000 profit

GRINDRUD RØRINSPEKSJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRINDRUD RØRINSPEKSJON AS

Who owns GRINDRUD RØRINSPEKSJON AS?

KNUT OLAV GRINDRUD is the largest registered owner, with 100.0%.

What is the revenue of GRINDRUD RØRINSPEKSJON AS?

GRINDRUD RØRINSPEKSJON AS had revenue of NOK 1.4m in 2025.

Who is the general manager of GRINDRUD RØRINSPEKSJON AS?

Øystein Grindrud is registered as general manager of GRINDRUD RØRINSPEKSJON AS.

Where is GRINDRUD RØRINSPEKSJON AS based?

GRINDRUD RØRINSPEKSJON AS has its business address in Lunde.

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.