biztrac. BETA
COMPANY REGISTER PROFILE
933629090 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

GEORGS NOTBØTERI AS

Org. no. 933629090 Limited company (AS) Tysvær Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 349,000
Operating profit NOK 103,000
Equity NOK −353,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−353k kr).

GEORGS NOTBØTERI AS is registered as a limited company in Tysvær, Rogaland with organisation number 933629090. 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 30,000, divided into 30000 shares. The company's stated purpose is: “Eiendomsutvikling, inkludert kjøp, salg og utleie av eiendommer, og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 349,000 in revenue and NOK 103,000 in operating profit.

Key figures · 2025

Revenue
NOK 349,000
▲ +360 %
Operating profit
NOK 103,000
▲ +147 %
Equity
NOK −353,000
▼ −129 %

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
2.0%
Weak
Return on total assets
Solidity
-6.9%
Weak
Equity as a share of total capital

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

Who owns GEORGS NOTBØTERI AS?

GEORGS NOTBØTERI AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about GEORGS NOTBØTERI AS

Who owns GEORGS NOTBØTERI AS?

HETTERVIK RESERVOIR CONSULTING AS is the largest registered owner, with 33.3%.

What is the revenue of GEORGS NOTBØTERI AS?

GEORGS NOTBØTERI AS had revenue of NOK 349,000 in 2025.

Where is GEORGS NOTBØTERI AS based?

GEORGS NOTBØTERI AS has its business address in Hervik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.