BIZTRAC BETA
Civil engineering activities

BOSSE CONSULTING AS

Org. no. 931057189 Limited company (AS) Åmot Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 694,000
Equity NOK 1.6m
Incorporated 2023
Share capital NOK 30,000

BOSSE CONSULTING AS is registered as a limited company in Åmot, Innlandet with organisation number 931057189. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Teknisk konsulentvirksomhet innenfor anlegg og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 694,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 694,000
Equity
NOK 1.6m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns BOSSE CONSULTING AS?

GEIR OLAV LARSEN
BOSSE CONSULTING AS
NOK 2.3m rev. · NOK 694,000 profit

BOSSE CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOSSE CONSULTING AS

Who owns BOSSE CONSULTING AS?

GEIR OLAV LARSEN is the largest registered owner, with 100.0%.

What is the revenue of BOSSE CONSULTING AS?

BOSSE CONSULTING AS had revenue of NOK 2.3m in 2025.

Who is the general manager of BOSSE CONSULTING AS?

Geir Olav Larsen is registered as general manager of BOSSE CONSULTING AS.

Where is BOSSE CONSULTING AS based?

BOSSE CONSULTING AS has its business address in Rena.

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.