BIZTRAC BETA
Accounting and bookkeeping

GEILO RÅD OG REGNSKAP AS

Org. no. 995205637 Limited company (AS) Hol Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 9,000
Equity NOK 471,000
Incorporated 2010
Share capital NOK 100,000

GEILO RÅD OG REGNSKAP AS is registered as a limited company in Hol, Buskerud with organisation number 995205637. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Rådgivning, regnskapsføring, forvaltning av kapital, fast eiendom, konsulenttjenester, kjøp og salg, deltagelse i andre selskaper og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 9,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 9,000
Equity
NOK 471,000
Est. value
NOK 320,000

Financial health · 2025

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

Who owns GEILO RÅD OG REGNSKAP AS?

MAY BRITT SOLHAUG
GEILO RÅD OG REGNSKAP AS
NOK 2.3m rev. · NOK 9,000 profit

GEILO RÅD OG REGNSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GEILO RÅD OG REGNSKAP AS

Who owns GEILO RÅD OG REGNSKAP AS?

MAY BRITT SOLHAUG is the largest registered owner, with 70.0%.

What is the revenue of GEILO RÅD OG REGNSKAP AS?

GEILO RÅD OG REGNSKAP AS had revenue of NOK 2.3m in 2025.

Who is the general manager of GEILO RÅD OG REGNSKAP AS?

May Britt Solhaug is registered as general manager of GEILO RÅD OG REGNSKAP AS.

Where is GEILO RÅD OG REGNSKAP AS based?

GEILO RÅD OG REGNSKAP AS has its business address in Geilo.

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.