BIZTRAC BETA
Joinery installation

GRINHOFS BYGG SERVICE AS

Org. no. 833321242 Limited company (AS) Drammen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK −75,000
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

GRINHOFS BYGG SERVICE AS is registered as a limited company in Drammen, Buskerud with organisation number 833321242. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby snekkertjenester, inkludert, men ikke begrenset til, montering av dører, vinduer, kjøkken og andre interiørelementer, samt generelle bygg- og konstruksjonstjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK −75,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK −75,000
Equity
NOK 24,000
Est. value
NOK 365,000

Financial health · 2025

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

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

Who owns GRINHOFS BYGG SERVICE AS?

ANDRIS GRINHOFS
GRINHOFS BYGG SERVICE AS
NOK 1.0m rev. · NOK −75,000 profit

GRINHOFS BYGG SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRINHOFS BYGG SERVICE AS

Who owns GRINHOFS BYGG SERVICE AS?

ANDRIS GRINHOFS is the largest registered owner, with 100.0%.

What is the revenue of GRINHOFS BYGG SERVICE AS?

GRINHOFS BYGG SERVICE AS had revenue of NOK 1.0m in 2025.

Where is GRINHOFS BYGG SERVICE AS based?

GRINHOFS BYGG SERVICE AS has its business address in Krokstadelva.

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.