biztrac. BETA
COMPANY REGISTER PROFILE
993864064 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Non-specialised retail sale of predominately food, beverages or tobacco

GRO SKEIMO AS

Org. no. 993864064 Limited company (AS) Arendal Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 25.3m
Operating profit NOK 345,000
Equity NOK 301,000
Incorporated 2009
Employees 9
Share capital NOK 250,000

GRO SKEIMO AS is registered as a limited company in Arendal, Agder with organisation number 993864064. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2009 and has 9 registered employees. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Dagligvarehandel og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 25.3m in revenue and NOK 345,000 in operating profit.

Key figures · 2025

Revenue
NOK 25.3m
▲ +4 %
Operating profit
NOK 345,000
▲ +56 %
Equity
NOK 301,000
▲ +0 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
1.18
Satisfactory
Current assets ÷ current liabilities
Profitability
16.7%
Very good
Return on total assets
Solidity
14.7%
Satisfactory
Equity as a share of total capital

Who owns GRO SKEIMO AS?

GRO SKEIMO AS
NOK 25.3m rev. · NOK 345,000 profit

GRO SKEIMO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRO SKEIMO AS

Who owns GRO SKEIMO AS?

Gro Skeimo is the largest registered owner, with 100.0%.

What is the revenue of GRO SKEIMO AS?

GRO SKEIMO AS had revenue of NOK 25.3m in 2025.

Who is the general manager of GRO SKEIMO AS?

Gro Skeimo is registered as general manager of GRO SKEIMO AS.

Where is GRO SKEIMO AS based?

GRO SKEIMO AS has its business address in Staubø.

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.