BIZTRAC BETA
Rental and operating of own or leased real estate

GK BOLIG AS

Org. no. 933380475 Limited company (AS) Klepp Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 54,000
Operating profit NOK 30,000
Equity NOK 705,000
Incorporated 2024
Share capital NOK 200,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GK BOLIG AS is registered as a limited company in Klepp, Rogaland with organisation number 933380475. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Kjøp, utvikling, utleie og salg av egen fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 54,000 in revenue and NOK 30,000 in operating profit.

Key figures · 2025

Revenue
NOK 54,000
Operating profit
NOK 30,000
Equity
NOK 705,000
Est. value
NOK 553,000

Financial health · 2025

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

Who owns GK BOLIG AS?

GRUDE & KLINGSHEIM EIENDOM AS
GK BOLIG AS
NOK 54,000 rev. · NOK 30,000 profit

GK BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GK BOLIG AS

Who owns GK BOLIG AS?

GRUDE & KLINGSHEIM EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of GK BOLIG AS?

GK BOLIG AS had revenue of NOK 54,000 in 2025.

Who is the general manager of GK BOLIG AS?

Fridtjov Middelthon is registered as general manager of GK BOLIG AS.

Where is GK BOLIG AS based?

GK BOLIG AS has its business address in Klepp Stasjon.

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.