BIZTRAC BETA
Rental and operating of own or leased real estate

GLYNITVEIEN 28 AS

Org. no. 925616230 Limited company (AS) Bamble Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 633,000
Operating profit NOK 587,000
Equity NOK 7.9m
Incorporated 2020
Share capital NOK 151,000

Signals

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

GLYNITVEIEN 28 AS is registered as a limited company in Bamble, Telemark with organisation number 925616230. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 151,000, divided into 150729 shares. The company's stated purpose is: “Selskapets virksomhet er å eie, drive, kjøpe og selge fast eiendom, inneha eierandeler i selskaper med samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 633,000 in revenue and NOK 587,000 in operating profit.

Key figures · 2024

Revenue
NOK 633,000
Operating profit
NOK 587,000
Equity
NOK 7.9m
Est. value
NOK 6.8m

Financial health · 2024

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

Who owns GLYNITVEIEN 28 AS?

OLADA INVEST AS
GLYNITVEIEN 28 AS
NOK 633,000 rev. · NOK 587,000 profit

GLYNITVEIEN 28 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GLYNITVEIEN 28 AS

Who owns GLYNITVEIEN 28 AS?

OLADA INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of GLYNITVEIEN 28 AS?

GLYNITVEIEN 28 AS had revenue of NOK 633,000 in 2024.

Where is GLYNITVEIEN 28 AS based?

GLYNITVEIEN 28 AS has its business address in Stathelle.

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.